Within Creo itself, particularly when used in relations, there is no sensitivity to case. In fact, even in relations I've written with the mixed case I defined the parameters with, the code only shows lower case.
For example, if I define a parameter as numParts and make a relation like "numParts = 2 + numAsm", if I re-edit the relations later the equation will be "numparts = 2 + numasm".
So the case of the characters in a parameter name don't really matter in terms of access to values in Creo. The same is true of file names and such, too.
@KenFarley Yes I agree with your statement that if the name is being used in relations, there is no sensitivity to case.
But I have one auxiliary application where it creates files on the disk with the same name as creo parametric model file name is (of course with different extension).
So user's expectation would be, if he has provided MyTestFile.prt then he would expect MyTestFile.ext and not mytestfile.ext or MYTESTFILE.ext .
The thing is, I don't think Creo even stores the parameters with the mixed case names I enter. I have a part that I built and it had parameters like angLock, DescriptionBOM, DesignBy, diaSlot, htLock, etc. When I open up the Parameters dialog to modify one of the values, they are listed as ANGLOCK, DESCRIPTIONBOM, DESIGNBY, etc. All the nice readable mixed case names are now FORTAN-ish all caps. Any specification of mixed case letters used to define the parameters is lost when they are saved, it seems. It's saved for the parameter values, but apparently not the names of the parameters.
As far as file names go, that has long been an annoyance. The value of rel_model_name() is always returned in all caps, regardless of what the "real" file name is. I guess they'd say "oh, but it's not the file name it's the model name" but then there is no function that lets you get the actual file name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
