Unfortunately once you SAVE in Solid Edge you loose all your "undo" capability. This has been a flaw in SE Developments thinking for years. Although I understand their logic, it does not take into account that there are times when this capability is still wanted. During the design phase we all make many features that just don't work out as planned, so going back while maintaining your undo capability is a very real need. Your example is a perfect scenario.
But when you are doing more elaborate design changes, you may make a dozen or so changes to a part. You are then faced with the tough decision if you save your work now, you'll loose this ability to go back.
So here's what I do. If I'm going to make major changes I first do a SAVE of the original. Then as I make my changes and then use the SAVE AS and change the name. The Original file stays as opened, so you can always get back to your starting point. This is really only good for when dramatically changing a parts design. The downside of this workflow is that you're left with a lot of different versions of one part that you don't need nor want in the end. So again for one or two changes it's a pain not having the Undo.
The requested SAVE while maintaining the "undo" file capability is still stuck on some User Enhancement Request list. Let's hope Development is listening.
Hi, I've recently run into this same issue. I assume there is still no work-around, but a solution is desperately needed. Even opening a block and closing it, making no changes, clears the undo cache. Please, there has to be some way to change this behavior. I'll learn to script, if I need to. There are times where the model updates, with unexpected results, beyond repair, when one or two levels undone would replace hours of work.
It seems like the clearing of the cache is an intentional design "feature," but has anyone ever been glad they can't undo something? Saving a model to any file, same name or otherwise, shouldn't effect any aspect of the model or program, except the "project has not been saved in x minutes" dialog, but that seems to be the only thing that doesnt care. As long as a file is open, it should, essentially, be a unique instance, when saved, a file is written, somewhere, open document stays uneffected, rather than overwriting the current running code, which seems like the only reason the undo cache is cleared.
no real questions here, just needed to vent to someone who might actually be able to do something about it.... Thanks.