When you write a parameter in a text string, ¶meter_name, is there a when to let the text know that the parameter is done other than a space? i.e. ¶meter_name_COLOR where Parameter_name is the name of the parameter and _COLOR is attached to the end (without a space between them).
Thanks, Dale
Dale, you can fool the system by using the old world delimiting with the curly braces "{0:&variable}".
In this manner, you can void the spaces all together.
This is from here:
Antonius Dirriwachter wrote:
Nono... I meant write a note that is independent of the hole itself. You might be able to assign some of the variables in a note, but even that has gotten harder.
My favorite method is to use a radial dimension and edit to a hole note. That way, the leader will remain normal to the edge.
I also a issues with the SAE callouts where spaces are added at the dash (UNC-2B reads UNC - 2B). Funny enough, there is a way to avoid the excess spaces:
Also found this:
If you have a string of variables like in hole callouts, you noticed that you require spaces between the end of the variable and new text characters. This is why you see...
&THREAD_SERIES - &THREAD_CLASS
UNF - 2B...a text string which is obviously not to any standard that we as engineers accept.But there is a little known method to remove the requirement for the space:
{0:&THREAD_SERIES}-{1:&THREAD_CLASS} ...which returns
UNF-2B
Old school editor but this is what makes it work.
Why didn't PTC do this for the hole CALLOUT_FORMAT?
PTC, are you listening? This is what "we" call fit and finish
I know we have discussed this before but I need to find it again.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
