I don't disagree with you, but not letting people know what is and is not happening is a problem as well. At least the current 'Save-As' behavior does let you know that 'changing the name' of a Component is also potentially changing the Assembly as well and you can either keep the current name for your Assembly, by doing nothing, or stopping and entering a new name and continue with the process. Perhaps we could do a better job, but IF you read the Status and Cue line and the look at what the dialogs that pop-up are really doing as well as the messages that appear on the screen, we are telling the user exactly what he needs to know while all this is happening.
As for your contention, that we need a 'Make Unique' while doing I 'Save-As', I disagree 100%. Don't mess with the 'Make Unique' as it's doing exactly what it was intended for. If I were to propose anything it would be perhaps a simple 'Rename' function which would ONLY work on the part selected but that it would act like 'Save-As' in that it would affect all the instances of the Component in the Assembly, but you would not be given the option to do a 'Save-As' for the Assembly, just leave it as a separate operation that's now fully the responsibility of the user to perform himself or not at a later point in time if he so desires. So you have a choice, we either FORCE you make a decision concerning the status of the now changed Assembly, at the time that we caused it to change, by doing a 'Save-As' on a Component, or we let never mention it, even though it still happened, and we'll assume that you'll not only KNOW what to do, but WHEN to do it. What's it going to be? Play it safe and ram it into your face. Or make it hidden and hope you understood what really happened.
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
