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
If we couldname objects(especiallyfaces), we mightanticipatereplacingcomponant=>The software coulduse theIDto replace thereferenceconstraintswithout error.
I know iMates, but the workflow is complex for many users.
I know also, that every object has an ID readable from API.
If we had this ID displayed and editable from constraint dialog and also reachable via the context menu on componant, it would be easier to copy ID from the "old" componant to the "new" component.
jletcher,
reference constraints => it's a "copy-paste" error. It should read : The software could use the ID to modify constraints without error.
We can use the iLogic solution to replace the object for constraint. At first the object should be assigned using entity name, and the entity name can be used for iLogic rule. Does it work for you?