I can see why, now. For instance, a symbol, like sd47, or d53, would be obviously an angle or a linear dimension and Creo would understand that. However, if the relation had a line that read,
Code:
x = Cos(THETA) + BETA * Sin(THETA)
Creo would understand that the trig functions imply that THETA is an angle, but, BETA is ambiguous in that respect...It could be either.
The rest of this post is purely hypothetical, I suppose:
The only way for Creo to scale linear values in a relation WOULD be if the syntax for applying units was used, as in;
Code:
x = Cos(THETA[deg] + MyScale * Sin(THETA[deg])
where MyScale is implied to be unitless since it has no specified units.
If Creo is allowed to ASSUME unitless parameters when all other parameters have SPECIFIED units applied by the user, then Creo SHOULD have no problem using Scale Model and applying it at the relation level, so long as the user makes sure he/she applied all the units correctly. But that is academic. That would just be a standard programming debug problem.
There IS the following option available for a config file as outlined in the Help system:
Code:
relations_units_sensitive [yes*, no], Checks for units when solving relations.
yes—Takes units into account. If units are missing, a warning appears.
no—Ignores units.
I have not tried this before, and my first question is, would Creo raise a warning for unitless parameters where required, like for any scalar?
BUT, there is still one caveat, and I do not see how this one could be easily dealt with. ASSUMING the above would even work in principle, Creo still would not understand what order to apply the scaling to the relations. For instance, I have certain "virgin" part files that have numerous relations in them that have default values applied. I wrote a vb program to calculate new values for the parameters and it builds the new relations as text files, when I want to modify those virgin parts for specific uses. I then copy/replace that text into each relation. UNFORTUNATELY, those relations must be modified in a definite order and usually NOT in the order that they occur in the feature tree. Depending on how I modify the virgin part for a particular usage, I sometimes find that I even have to change the usual order by trial and error to get regens to work properly.
So there is really no way for Creo to know what to do in those cases, SOOOOOOOO, it is probably always best that Creo simply leave relations alone when scaling a model. Unless PTC can figure out a way to have those relations modified in any order without regen failures.