Undocumented Feature for 2005?
Undocumented Feature for 2005?
(OP)
Read this slow - cause it's confusing 
I have a part - with 2 configs. I place that part in an assembly & pattern it. Then set-up 2 configs to control the configs of the parts. Then make a second assembly & insert the first assembly. Now I can expand the feature manager - in my second assembly - expand the tree & get to the original part - within the sub-assembly. Here I can change configs of the part... without opening the sub-assembly for editing.
This is a bad thing to do IMHO. I didn't remember that this was a capability of 2004 & called tech support to confirm. After convincing Junior-CAD-Jock that I was right (I love when that happens) - he tells me it's not a bug, but an added capability for 2005 & there's no way to toggle it off.
BTW - we still have a few slackers on 2004 & I double-checked this on one of their PCs.
Can anybody else confirm this?
I do not like it & want it to go away
I have a part - with 2 configs. I place that part in an assembly & pattern it. Then set-up 2 configs to control the configs of the parts. Then make a second assembly & insert the first assembly. Now I can expand the feature manager - in my second assembly - expand the tree & get to the original part - within the sub-assembly. Here I can change configs of the part... without opening the sub-assembly for editing.
This is a bad thing to do IMHO. I didn't remember that this was a capability of 2004 & called tech support to confirm. After convincing Junior-CAD-Jock that I was right (I love when that happens) - he tells me it's not a bug, but an added capability for 2005 & there's no way to toggle it off.
BTW - we still have a few slackers on 2004 & I double-checked this on one of their PCs.
Can anybody else confirm this?
I do not like it & want it to go away
SolidWorks 2005 SP03.0 / Windows 2000 Professional






RE: Undocumented Feature for 2005?
Why do you think it's bad? I think it's because if a subassembly is alredy validated, you have the risk of change it without knowing. I think the only protection available is to have the files write protected (by the OS) and and check to open refenced documents with read-only access and check to discard changes in read-only documents.
Regards
RE: Undocumented Feature for 2005?
I believe you should have ro RMB the sub-assembly & open it for editing before changing the part configs all "willy-nilly"... just don't make sense to me. I'm still working out the details of how to protect my standard assemblies now. They're already WRITE/PROTECTED by the OS, so I don't think there's any signifigant danger. Bt it's still an a$$-backwards way to control it.
Are you confirming that it is a new feature & there's no way to toggle it off - like a SYSTEM PROPERTY?
RE: Undocumented Feature for 2005?
I don't recall any system option to disable this. The OS write protection is the only secure way to protect files. Even with the second method (check open referenced documents with read-only access and check to discard changes in read-only documents) you can force SW to save changes!
You are right, it should have an option to disable this, or the options alredy available shouldn't let you force the save.
Regards
RE: Undocumented Feature for 2005?
It not a new feature and still requires a conscience effort to be able to change configurations located deep within the tree.
And if you are able to find this command, I would believe you should also be able to understand that you are going to change whatever sub-assembly it resides in. That's why they called it a "TREE".
Remember...
"If you don't use your head,
your going to have to use your feet."
RE: Undocumented Feature for 2005?
I may be going out on a limb here, but I doubt that I've taken leaf of my senses & I hope I'm not barking up the wrong tree
RE: Undocumented Feature for 2005?
Drill down anywhere in the tree,
RIGHT-CLICK - PROPERTIES - CHANGE ACTIVE CONFIGURATION
Changing configurations through the feature manager tree this way has been there a long, long time.
Remember...
"If you don't use your head,
your going to have to use your feet."
RE: Undocumented Feature for 2005?
RMB to change configs of a part within a sub-assembly (without opening that sub-assembly for editing) - NO...
...not according to my testing of a PC running 2004 & my PC running 2005.
Either we're talking about 2 different things - or we just have to agree to disagree.
You dudes can sort this out for me while I'm on vacation
RE: Undocumented Feature for 2005?
TateJ: Yes, this is an added capability of 2005 and I think it is documented somewhere. I don't see any problem with it.
RE: Undocumented Feature for 2005?
Can I dis-able it?
... That's the question of the day.
RE: Undocumented Feature for 2005?
I don't see the SW2005 method as a problem. It is not as though it is an action which can be done inadvertantly. A person would have to know that they were selecting a new config'.
However, one possible workaround might be to create a part config' which is not used in any assy, make sure that it is the active config when the part is saved and make the part Read only. That way the parts config' in an assy/sub-assy will not be able to be changed without changing the parts status.
Making the best use of this Forum. FAQ559-716
How to get answers to your SW questions. FAQ559-1091
Helpful SW websites every user should be aware of. FAQ559-520