pirateincognito
Automotive
- Mar 4, 2015
- 20
thread561-433964
This is an issue that needs to be filed with GTAC.
I cannot do it at the moment because I'm having account issues.
Current NX11 (local not TCE) behavior is multiple Save As dialogs popup when you only want to save a single child component.
There are no UI queues to explain what is happening. The title bar in Save As diaglog doesn't indicate you are now saving the Parent.
There is no Save Scope to choose from. The Options button is greyed out.
It's very confusing to the user and it's not clear what is happening.
Only when you hit cancel on the 2nd Save As dialog, does NX prompt you that the parent assembly won't be saved with a new name. Are you sure you want to do this? Yes/No?
This workflow needs to be addressed and reflects poorly on modern NX that such an old and fundamental process isn't straight forward.
There should also be an option to Save As but not replace the component in session with the newly Saved As file. CATIAV5 calls this function Save a Copy.
This is an issue that needs to be filed with GTAC.
I cannot do it at the moment because I'm having account issues.
Current NX11 (local not TCE) behavior is multiple Save As dialogs popup when you only want to save a single child component.
There are no UI queues to explain what is happening. The title bar in Save As diaglog doesn't indicate you are now saving the Parent.
There is no Save Scope to choose from. The Options button is greyed out.
It's very confusing to the user and it's not clear what is happening.
Only when you hit cancel on the 2nd Save As dialog, does NX prompt you that the parent assembly won't be saved with a new name. Are you sure you want to do this? Yes/No?
This workflow needs to be addressed and reflects poorly on modern NX that such an old and fundamental process isn't straight forward.
There should also be an option to Save As but not replace the component in session with the newly Saved As file. CATIAV5 calls this function Save a Copy.