-
Re: Delete components from subassembly - behavior changed?
Okay, just after posting this, I found this in another post:
"I see you're on 2009 and wanted to let you know that 2013 has updated this workflow. Now when you delete a component, only that component is deleted, not the entire sub-assembly. Big improvement over having to edit the sub-assembly and then delete the component."
So it looks like it *is* changed. I don't like it - it's not always apparent that a component in the graphics window is in a subassembly, and there's nothing to notify you that you're modifying another file. Seems like an easy way to unintentionally make a mess of my assembly files.
-
Re: Delete components from subassembly - behavior changed?
I would bet the reason for not having a notification is that if you wanted the part deleteed, you want it deleted reguardless of what assembly/sub-assembly it is in.
I have does this a few times already, and hadn't caught on to the change!
-
Re: Delete components from subassembly - behavior changed?
Agreed, that is a major mistake and a huge headache that SW has created for its users. It should be put back to the old 'workflow' ASAP.
-
Re: Delete components from subassembly - behavior changed?
Really SW? You thought this was an improvment in workflow? Booooo.
-
Re: Delete components from subassembly - behavior changed?
Another person on the complaint bandwagon.
Hurray!
The more complaints the more likely we get an actual fix and not a halfa$$ one.
-
-
-
Re: Delete components from subassembly - behavior changed?
I just ran across this the same way. Fortunately I noticed the "weird" behaviour before I got too far.
This is really an accident waiting to happen. SW should have put in a default dialog that notifies you if you are deleting a part in a sub-assembly in your current document assy. You can always elect to discontinue the dialog when you feel you have a handle on the new behaviour. Also, you might want to leave a warning dialog on permanently as a tool. I just finished going thru an old assembly with several hundred parts and cleaning out old parts. It was way slower and very tedious. All you have to do with this new behaviour is select a part and not remember to check it in the tree and you have damaged a sub-assy. Or worse yet you try to window a bunch of parts and grab one you didn't intend to "nick" and you damage a sub-assy.
I really didn't think that right click->edit assembly was such an onerous task that I would throw out the safety of keeping my sub-assemblies undamaged.
-
Re: Delete components from subassembly - behavior changed?
Yeah, I saw that in the 'What's new' and flagged it as a potential problem. I agree that it shouldn't be set this way by default because it stands to reason that I can remove a subassembly from an assembly affected by an ECO, but the subassembly may not be included in its scope.
-
Re: Delete components from subassembly - behavior changed?
This also has changed the way you pick and delete parts from an assembly. If you have a sub-assembly and you want to delete it you MUST go to the tree and select the sub-assy (or right click->select sub assembly), or you are only deleting a PART inside the sub-assy. At least undo works for this case.
I also discovered that this is affecting drag and drop. If you are dragging a part in the tree up or down for whatever reason, be sure you see where it ends up. You can drag a part from the top level assy you are working on and drop it into a sub-assy by mistake. If you aren't sure which sub-assy you lost the part into, you go looking for it. There is no undo. The good news is that you can drag it back, but your configurations may no longer be correct, so you have to check them.
I am unable to see a purpose in this functionality. The movement of parts from one assy to another for whatever reason can be accomplished in other ways that are less dangerous to those subs that you want to remain untouched. If I want to work in an assembly that is just a mass of parts with no sub-assemblies I would build it that way, or dissolve the subs that need to be parts inside the top level assy.
-
-
-
Re: Delete components from subassembly - behavior changed?
This is absolutely horrible! I am glad I discovered this in the design stage. With a company as large as mine, and we are not that big, catastrophic damage could incur. I designer could accidentally highlight the wrong part and delete it from a sub-assembly, unaware that they just edited not only that sub-assembly but the whole drawing associated with it! And with there being no way to undo what you just did, you have to go back and rebuild said assembly. I can't think of a more damaging change. This equates to re-learning the software.
-
Re: Delete components from subassembly - behavior changed?
Derek Smith wrote:
And with there being no way to undo what you just did, you have to go back and rebuild said assembly.
I don't like the feature either, but I'm pretty sure that the Undo button will work, assuming you hit it immediately and haven't saved or rebuilt.
-
-
Re: Delete components from subassembly - behavior changed?
This is one of the WORST THINGS Solidworks has ever done to us.
I just got bit by this pretty bad. I didn't know what was going on until it hit me about this change.
I had to track back and reconstruct an assembly that was goofed up while inside another assembly and things were deleted/supressed.
I can't believe they thought this was a GOOD thing!!!!
Please give us an option to turn this behavior off. At least pop up a warning box telling us what we are about to do.
I'm shuddering to think what some less experienced users here might have done not knowing.
-
Re: Delete components from subassembly - behavior changed?
Is there an option somewhere to revert back to the old behavior?
AGAIN, I just ran into an assembly where all parts were deleted inside of it and saved inadvertently.
I almost don't trust using sub-assemblies anymore.
-
Re: Delete components from subassembly - behavior changed?
Andy,
You can go vote for SPR 697503.
Paul
-
-
Re: Delete components from subassembly - behavior changed?
Anyone have any info on this? This "change" bites me more than I would like to admit. Did they fix it in 2014?
-
Re: Delete components from subassembly - behavior changed?
Not that I can see. 2014 works the same. There may be some way to turn the behaviour off but I don't see it and I doubt that it is there.
Just today I had an assy in an assy. This one sub-assy had one part in it. As I was cruising I windowed and then deleted the part. Then I realized that was probably a mistake and looked at the tree and sure enough the part was still in the tree but it was now empty.
You just have to be constantly aware of what you are doing if you delete or drag and drop. It doubles the checking you have to do when removing parts, as you have to look at the tree to make sure you got it right. You cannot assume what you *think* you deleted was deleted.
-
Re: Delete components from subassembly - behavior changed?
Lyn, Kirk, et al,
Vote for the SPR that Paul mentions (SPR 697503).
Jerry S.
-
Re: Delete components from subassembly - behavior changed?
Where do I find that? I don't know what an SPR is.
-
Re: Delete components from subassembly - behavior changed?
Log in to your customer portal and go to the enhancement request page and search for 697503. I don't see where you get to "vote" on this. I have never found it either, and the boss seems to want me to work on other things.... imagine that.
Here is what I found.
I notice that 664042 is to be available in 2014 b2. It says this: "Implement an option that allows you to choose whether an entire sub-assembly or only the component is deleted when selecting a component of a sub-assembly and pressing Delete".
There is also a note that says: "Refer to followup SPR 697503 for the UI option enhancement request. A workaround is possible for this issue however. Please contact your reseller for further information."
So you have to have support to get this fixed? Maybe they are just going to tell you to be more heads up and do your deleting from the tree, I don't know.
On the other hand there is 697503 which says: "Create an expanded delete box to allow you to choose to delete either a component or a entire subassembly while deleting items in an assembly" and it is fixed in 2015 a1.
So it appears that these issues are addressed if you have the latest SW (2015 a1). Stay tuned...
-
Re: Delete components from subassembly - behavior changed?
I like the new behavior.
Face it, it’s a coin toss. SW needs to recognize coin tosses and provide for both sides of the coin. To me… this warrants an on screen alert. Just don’t make it too wordy, OK? Like delete: “part” or “assy” seems plenty descriptive to me. If you want something to put in options, choose default part or default assy.-
Re: Delete components from subassembly - behavior changed?
I completely agree with this. If they are going to change something like this give me a check box in the options to allow me to revert back to the way it was.
-
-
Re: Delete components from subassembly - behavior changed?
"A workaround is possible for this issue however. Please contact your reseller for further information."
Does anyone know what they mean by a workaround? Just living with it? I am asking because I am in a company who's solidworks upates are driven by our pdm system so we won't be upgade to 2014 or 15 any time soon. We already contacted our var once about this issue but that ticket got closed since the behaviour was intended by sw. So if there is a work around that will actually change this behavior I'd contact our var again. Just wondering if anyone has tried this "workaround".
-
-
-
-
-
-
-
Re: Delete components from subassembly - behavior changed?
How does one go about voting for an SPR? It seems to be extraordinarily well hidden on the website.
-
-
Re: Delete components from subassembly - behavior changed?
Thanks Paul, I never would have looked there.
-
-
Re: Delete components from subassembly - behavior changed?
I've never been more frustrated with Solidworks than I have been in the past couple releases, especially 2014. I've been using since release 97 plus.
My patience is starting to run short.
-
Re: Delete components from subassembly - behavior changed?
Apparently, they limit the length of user comments, but don't bother to tell us. It generates an error if you rant on too much.
-
-
-
-
-
-
-
Re: Delete components from subassembly - behavior changed?
Our company just upgraded from SW12 to SW14. Haven't heard any of the 30+ engineers here say they like this feature. It has bit almost all of us at least once (some more than once). Probably the biggest pain upgrading to SW14. Hopefully they make an option to switch between deleting the assembly or the component. I don't understand why that wasn't done in the first place.
If it makes sense for a person to always delete the component, make a checkbox in the System Options to make that happen, not just change it for everyone and hope it all works out.
-
Re: Delete components from subassembly - behavior changed?
The worst part about this is that we may not ever really know how many time we have been bit by it. In a pdm system one might check out a top level assembly in order to delete a component and not realize the component is in a subassembly. You check it back in, but since the subassembly wasn't checked out, you haven't actually changed anything. I could see this happening on a regular basis with nobody being the wiser. It would seem that whoever came up with this idea needs a lesson in scope handling.
-
Re: Delete components from subassembly - behavior changed?
It gets even better when you have new people coming in, or ones who are not super CAD users. It gives that warm fuzzy feeling when you insert a sub-assembly that is EMPTY, because someone deleted the parts in their top level assembly, and that sub-assembly has to be re-created from scratch, or you have to postpone your work while IT goes to the backups and finds that part for a restore. Since we use it all over the place, and it is linked to a bunch of other assemblies, both new and legacy, this has to be done. Of course the pain isn't over yet. If you open an assembly where the damaged sub was used, and you had to re-create it, then you get to go find it and re-mate it into the right location; if you know what the right location was. Of course with hundreds of parts you may get to dig out the old PDFs and find where this sub was placed exactly before you can do that. At that point you can continue with what you started out to do. Ahhh, the enhancement that keeps on giving!! <cough>
-
-
Re: Delete components from subassembly - behavior changed?
This is a repost, but this thread seems to have garnered some interest again.
From the knowledge base...
"A workaround is possible for this issue however. Please contact your reseller for further information."
Does anyone know what they mean by a workaround? Just living with it? I am asking because I am in a company who's solidworks upates are driven by our pdm system so we won't be upgade to 2014 or 15 any time soon. We already contacted our var once about this issue but that ticket got closed since the behaviour was intended by sw. So if there is a work around that will actually change this behavior I'd contact our var again. Just wondering if anyone has tried this "workaround".
-
Re: Delete components from subassembly - behavior changed?
Have not tried the workaround, but have been able to see SW 2014 SP02. In this version you get a pop up dialog box that asks you if you are sure if you want to delete the item. It lists the sub-relationships (mates) also, why I'm not sure. I'm not sure where this is supposed to take us. It is too easy to just punch the "yes" button when you are moving fast. There is also a check box to not show that dialog again, but then you would be back to ground zero and flying without a parachute. I would still much rather see a system setting that disables the behaviour completely. Just my 2 cents.
-
Re: Delete components from subassembly - behavior changed?
So would you say that they did not include this functionality mentioned in this spr either? (the ability to choose to delete the whole subassembly)
SPR 697503: Create an expanded delete box to allow you to choose to delete either a component or a entire subassembly while deleting items in an assembly
-
-
-
Re: Delete components from subassembly - behavior changed?
My 2 cents:
Instead of giving us another stupid dialog that will probably get permantly dismissed and always pops up in the part of the screen you are currently not looking at, add a modifier key e.g. shift+delete that deletes the part regardless of scope, and put the standard delete back the ways it should be.
-
Re: Delete components from subassembly - behavior changed?
That would work too.
This year long thread without huge participation makes me wonder, as an aside, how many people actually use the software beyond drawing rectangles and extruding them .1 inch. I would think the forum would be on fire. Just sayin'.....
-
Re: Delete components from subassembly - behavior changed?
It has shown up in a couple other threads, but I think like you say a lot of people don't pay attention to what is going on in Solids especially when it comes to workflow changes. These "blind users" are the same people that are likely to get bit by this and cause problems for others, but also are not likely to complain about the issue but rather blame it generically on their computer.
-
Re: Delete components from subassembly - behavior changed?
I've been a SW user since SW98+.
I was SO used to the old sub-assembly delete workflow that this change has burned me and other users more times than I can count.
For some reason it's really easy to do this and not notice. So, some kind of in-your-face flag as to what SW is about to do to you is absolutely necessary.
Maybe a big group of users don't use sub-assemblies much?
It boggles my mind that this is the behavior they intended and thought we wanted.
-
Re: Delete components from subassembly - behavior changed?
As I said above, in my opinion, a flag (i.e message box) is annoying. But I agree that deleting a part regardless of its scope is dangerous and should be thought about before it is done. If you think about it, its essentially the same as deleting a feature from a part when you intend to delete only the part. When, you actually want to delete a feature you need to look at were the part is used etc. which means you should be editing in the scope of the part.
This is why I think that they should just change the behavior to the way it always was (no flag, just delete the entire assembly), and if anything add a modifier key (shift del) for deletion regardless of scope. Like in windows explorer (shift delete skips the recycle bin)
P.S. I think we are both on the same page, but I'm just doin my part to keep the conversation going so that it gets noticed
-
Re: Delete components from subassembly - behavior changed?
I like Matthew's approach on this one. I would like to see a toggle buried in the system settings for this one, like a lot of other user preference/workflow options.
You get used to working a certain way and when you are really flying you may not want to stop and "examine" the part structure because the parts and all that are familiar and you know exactly where you are going and what you want to do while in there. For example, if I am working in a large rats nest of an assembly and I am used to seeing a commonly used valve and a commonly used base that it sits on, I am going to just delete the valve if it is the wrong one and insert a new and keep moving. Unless I stop and "examine" the model before making this change I might not notice that the creator of the assembly had set up a new sub-assembly with the valve and base together - a logical use of a sub assembly since it is a common pairing. Trouble is he's in New York and I'm in Oregon and I didn't know this as it is a new wrinkle and so I blow-up our company sub-assembly, and how many other assemblies that are referencing this "new" sub-assembly. And again, if I see this same popup too many times I am going to either disconnect it thinking I will remember, or I will start hitting OK out of habit...... a bad habit in this case.
It's REALLLLLL easy to screw something up even with the pop up, assuming you have the latest rev of SW 2014.
-
-
-
Re: Delete components from subassembly - behavior changed?
If you delete parts from the graphics window (as I do 75%+ of the time) you don't realize it's from a sub-assembly. It just looks like you're deleting any other part from the main. You get no feedback other than "do you want to delete this part yes/no". You may think "yes I want to get rid of this part" and poof, gone. Until you open the sub then find out what you did later.
When you're doing it from the tree, obviously you can see what's up and catch yourself. But that's not how I operate most of the time.
As I sit here, I'm suspicious how many assemblies I (or my co-workers) have murdered unknowingly :-/
-
Re: Delete components from subassembly - behavior changed?
I have caught myself doing this and the bad part is, you can't just hit undo. You have to go back in the sub-assembly and hit delete. I wish there was some way we could get solidworks' attention and have someone look into this issue. It has to be bigger than a couple of people complaining about it.
-
Re: Delete components from subassembly - behavior changed?
I think the easy fix (other than reverting to old workflow) is to have a popup that reads like this:
"The part you are deleting is part of a sub-assembly. If you delete this part, it will affect all other assemblies that it is contained in. Do you really want to do this? Yes/No."
And DON'T let us permanently dismiss the popup.
-
Re: Delete components from subassembly - behavior changed?
As long as we are discussing how things should work, what about multiple part selection for deletion, (like with lasso select). This has been rendered basically useless because of this issue. How would the popups work then? One for every unique subassembly? I can see this being really annoying for fastener subassemblies.
-
Re: Delete components from subassembly - behavior changed?
Honestly, if it's in a sub-assembly - give me a popup. I want to know. I don't care how many levels deep. That only makes it worse in my mind.
Like I said above, if you delete from the graphics window, you may not even realize it's in a sub. You just want it gone and you go for it. 5 saves later and you realize it. Or worse you never catch it.
-
Re: Delete components from subassembly - behavior changed?
Andy Sanders wrote:
Honestly, if it's in a sub-assembly - give me a popup. I want to know. I don't care how many levels deep. That only makes it worse in my mind.
Yes agreed, or just turn the thing off as has been suggested. You get a pop up if you have 2014 SP02, but if the function is that dangerous why on earth would you allow the user to permanently dismiss the warning? I can see CAD Admins tearing their hair out on that one. And I don't care how long you have been running SW, as software companies in general typically have the attitude of "just get used to it". No, that's not the solution to the problem. The problem is the function change was a bad idea and anyone working with assemblies will find out eventually - the hard way.
-
-
-
-
-
-
-
-
-
Re: Delete components from subassembly - behavior changed?
I have caught myself doing this also.
I think I've found a couple assemblies that are missing parts, and I suspect this is what happened.
We use many assemblies in our top level assemblies, and am afraid of how many times this may have happened.
I found and voted for the above enhancement request also.
-
Re: Delete components from subassembly - behavior changed?
See Attached Thread. Set macro to keyboard shortcut and use instead of delete.
-
Re: Delete components from subassembly - behavior changed?
Good suggestion Mark, but what I think most of us are facing is the actual ability to delete a sub-sub-sub component accidentally and not know it. We want that ability severely controlled or gone completely. With a macro you are still altering your habitual work habits to conform to a shortcut, when some of us have been using the delete key in SW and other CAD for 20 years....... that's a stiff order to change that habit.
-
Re: Delete components from subassembly - behavior changed?
I agree with Lyn. This is something that especially affects the "not so aware" users. Expecting them to use a macro instead of delete is a tall order indeed.
Bottom line:
New Workflow: Deleting sub-sub-component = Dangerous = should not be as easy as just punching the delete key
Fix: Somehow SolidWorks needs to make the user stop and think about what he's doing before allowing this operation.
Old Workflow: Deleting component from top level = relatively safe = delete key without prompt is just fine
Fix: preferably this workflow can be restored as it is relatively safe (the user can only screw up his own assembly)
-
Re: Delete components from subassembly - behavior changed?
I totally agree with you Lyn. I plan on modifying the macro so it will work in assems, part, drawings & sketches then I can set it to my delete key. I know this isn't the prefered way but it's a solution until they fix it. I just keep having this thought that they are going to program a window that pops up every time you hit delete and it will say "do you want to delete component or assembly?" So now one keystrike becomes two.
-
Re: Delete components from subassembly - behavior changed?
Mark Coville wrote:
I just keep having this thought that they are going to program a window that pops up every time you hit delete and it will say "do you want to delete component or assembly?" So now one keystrike becomes two.
You're too late!! That is sorta what you get in 2014 SP02. You get to confirm or cancel the action. Two keystrokes instead of one just to delete something (or not).
-
Re: Delete components from subassembly - behavior changed?
That box will still show up as well (unless you check do not show again). So it's up to 3 clicks now. It wouldn't be that big of an issue (the way it works now) if UNDO worked properly. haha
-
-
-
-
-
-
-
-
Re: Delete components from subassembly - behavior changed?
This is a nightmare.
Now I understand how we have been breaking so many assemblies.
Who on earth would want the 2013+ functionality? Who works like that? Clearly someone with nice little stand alone projects unlike us.
I have my widgets being built on the shop floor from my drawings and build instructions.
But most of my work is mounting these widgets in top level assemblies specific to my customers.
Since 2013 my production build drawings have been getting broken all the time. Its cost us hours.
I've voted for SPR 697503 - they wont like my language in the comment, and I'd like to congratulate my VAR for managing to stay polite during my recent phone call!
2015 will have a warning box that actually mentions something about sub assemblies, in 2014 SP4.0 the warning box is the same if the part resides in a sub assembly or a sub assembly many levels down, so it is really no use at all.
But a warning is not what is required. We need a check box, set by default, to restore the functionality that we know and understand. The crazy or "unusual workflow" people who wanted this current functionality can search out that check box and change it if they want!
Refer to followup SPR 697503 for the UI option enhancement request. A workaround is possible for this issue however. Please contact your reseller for further information
Any clue as to what this work round might be? My VAR has no idea... probably just setting assembly components to read only - I've been through all the different confusion levels of settings with that already.
Its enough to make me actually start using workgroup PDM - at least then stuff that hasn't been taken ownership of wont get broken. It might actually be worth the hassle...
-
Re: Delete components from subassembly - behavior changed?
Welcome to the club.
I agree with everything you said.
Whoever wants this behaviour doesn't know what they are doing.
I say bring back the old work flow -not even a check box.
You should have the ability to delete things not in your current editing scope, but it needs to be really obvious that that is what you are doing and it should be controllable not an on-off switch, and definitely should not be the default behaviour.
It should probably be a different key on the keyboard or a button that says "globally delete item from its local scope."
-
Re: Delete components from subassembly - behavior changed?
BTW, a pdm system doesn't make this issue dissappear. you just end up with extra parts. (people thinking they deleted a part, when it was really in a read only subassembly) Not quite as bad as empty subassemblies, but still an issue.
-
-
-
Re: Delete components from subassembly - behavior changed?
If we can learn it, we can select by using the right mouse click, and holding the C key down...then it lists all the sub assembly levels, and not the individual part in the bottom level
-
Re: Delete components from subassembly - behavior changed?
My VAR has supplied me with a registry hack that restores the pre 2013 behaviour.
I've not tried it yet, but his screen grab shows that when a sub assembly component is selected the default situation is it selects the sub assembly rather than a component within it.
-
Re: Delete components from subassembly - behavior changed?
Can you post the registry hack so that we can see if it works. Thanks.
-
-
Re: Delete components from subassembly - behavior changed?
Sorry for the delay, we finish early on Fridays
I just tested this myself (SW2014 SP4.0 Win7x64) and it appears to work. Default is it selects the sub assembly one below the top level in the active window.
1- Close SOLIDWORKS
2- Access the registry
by typing “regedit” (without the quotes) into the START menu- press
enter for the Registry Editor to appear.3- In here use the left
hand folders to navigateHKEY CURRENT USER > Software >
SolidWorks > SolidWorks 2014 > General4- Right click and
choose to export this “General” folder- saving it somewhere convenient (this is
a backup in case anything goes wrong).5- In the main screen
find the line item called “Delete top level Reference of Selected Component”Double click this and
set the value from 0 to 1
7- Click OK and close
the registry editor.8- Reopen SOLIDWORKS and
test the new workflow. As you can see from the image below I am showing me
deleting a part called “SSM PART 08” but the confirmation dialogue is
actually deleting the sub assembly this is held in SSM SUB ASSEMBLY
gGood luck, don't blame me if it goes wrong
-
Re: Delete components from subassembly - behavior changed?
Thanks Gordon! I tried it and it worked. (SW Prem. 2014 x64 SP4.0)
-
Re: Delete components from subassembly - behavior changed?
Does this hack work with both selecting items from the tree AND selecting them on-screen?
I've been a bit confused that it looked like some of these fixes only applied to selections from the tree, although I might have read it wrong.
-
Re: Delete components from subassembly - behavior changed?
Andy,
I would be tempted to just make the change and try it, assuming you have SW 2014 SP4 OR higher, as that is all that has apparently been confirmed as working with this change. If it doesn't work the way you like put it back the way it was. YMMV.
If you are not comfortable moving in the Registry then best wait for Gordon to answer.
-
Re: Delete components from subassembly - behavior changed?
It works the same way selecting parts on the screen or from the tree.
-
Re: Delete components from subassembly - behavior changed?
Thanks. I'll give it a try when I can carve out some time. I appreciate the info!
-
-
-
-
Re: Delete components from subassembly - behavior changed?
This is good Gordon. Thanks! Too bad everyone has to wait 2 years for a hack solution.
BTW, for those out there still using 2013.... you're outa luck. There is no such key in 2013. I checked on a machine with SW 2013 Premium Sp04.
-
Re: Delete components from subassembly - behavior changed?
That's a pity about 2013
...and yes two years and 8 or 9 service packs!?
BUT - how come it took me so long to notice what was actually happening to my sub assemblies?!
-
Re: Delete components from subassembly - behavior changed?
Don't go there. Just keeps you awake at night.
-
-
-
-
-
Re: Delete components from subassembly - behavior changed?
This really bugs me when making configurations!
When I decide to make a configuration of a top level assembly with many sub-assemblies I have to go into those sub-assemblies to make changes (suppress parts etc) and I feel it would be really handy to just be able to make one top level configuration where parts change rather than make several configurations through several sub-assemblies.
I can understand that modifying parts would be near impossible but merely suppressing components that are a few levels down I thought would be an option. If I do that though I end up with the part being suppressed through all top level configurations because the part was suppressed through all uses of the sub-assembly. It's a bit frustrating.
-
Re: Delete components from subassembly - behavior changed?
Just a reminder, that this has been fixed in SW2015. Now you get an option to delete the component or the subassembly and can even have that stick.
-
Re: Delete components from subassembly - behavior changed?
Alin,
I haven't had a chance to see 2015 yet.
Does "dont' show again" set all opened assemblies to the selected behavior?, and the only way to get it back, if you wanted to use the behavior, is to restore the dialog? Does this selection apply then to all assemblies opened in the future on this machine? or do you need to set this for every assembly you open?
How does a CAD admin set the behavior for new installs? Create an assembly and do something to make this dialog pop-up?
Thanks,
Lynden
-
-
Re: Delete components from subassembly - behavior changed?
I found this similar issue - you can change the config of a component within a sub assembly that isn't open for editing - in a similar way to how you could delete parts from that sub assembly. Not addressed by the work round.
For me one of the main points of sub assemblies is to keep track of what you are editing and what you don't want to edit. How SW have managed to loose sight of that I do not know!
I made a separate post here:
Accidental editing of sub assemblies that are not open for edit
-
Re: Delete components from subassembly - behavior changed?
We have people come in who are transitioning from other CAD packages (Pro-E, etc) and to my knowledge other packages do not allow you to do this type of "deep editing" so they don't know that they have hosed up a sub-assy.
They need to just remove this functionality along with "deep deleting".
-
