Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Support for non-shared project parameters should be removed as this would be the first step in allowing the name of a parameter to change. Wider than this suggestion however is that we work in a global environment so it should be possible for a shared parameter with a certain GUID to have many localised names. It is simple logic really.: If the parameter has a name specific to one language region then that gets used for all regions If parameter has a multiple names then the region specific one is used or default English (English is a good default for me...I don't have to do anything). Say I add a parameter name then transfer the project to my non-English counterpart they could then assign their own names in a second language (or I could do that to start with in my global content).
I wanted to note that setting Element.Name for Global Parameters is allowed and works. I would expect the code flow for Project Parameters to be similar and would hope that it wouldn't be hard to accomplish.
