Spaces are allowed in Windows for file names, they should be allowed in Creo Elements/Direct Modeling for part names.
-> Is now available with Release 20.0
And characters other than alphanumeric.
Do you mean Name like part number, or Name like Description?
I mean the "instance name" (the name that shows up in the Structure Browser).
Please see also http://communities.ptc.com/ideas/1907
With additional characters (e.g. blanks, Special characters) you are driving on a dead-end road,
because it will make it harder to move to CREO, which has very strict rules for names of parts/asssemblies.
Very strict rules are often the source of trouble especially in theis context. Think of countries like germany and others with some umlauts.
Maybe PTC should rethink if the wish for the expanded character set or the strict rules are a dead-end road.
release 20 adds (allows) blanks *and* the + (plus) sign in the part name.
Currently, Creo Parametric does not support file and feature names greater than 31 characters (Unite supports up to 75 characters), white spaces, special characters and mixed cases. This limitation also impacts areas within Creo; such as dialogs, relations, family tables, model tree, etc. As a result of this limitation, names are truncated, or not allowed, which presents a major usability issue raised by users.
PTC is aware of these limitation and is currently researching efforts to remove the naming restrictions in a future release.
As part of this effort, PTC will hope to deliver a solution that will support names up to 179 characters, spaces and special characters. The plan will be to remove these restrictions in file names, model names, features, parameters, Model Tree, dialogs, family tables, layers, toolkit, Unite and all other areas impacted by this limitation.
As for Creo Elements Direct, this will need to be reviewed.
Sr. Director, CAD Product Management
Many Creo Parametric (Pro/E) users are waiting for about twenty years for the emergence of the support of file and feature names greater than 31 characters. It would be nice to outline at least some specific time frame for the appearance of this functionality ... in this decade, over the next two or three decades ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.