personally, I think this is one of the biggest faults. it relies on the user to know that there is a config setting in order to get access a desired feature. it's a chicken/egg scenario. you can you know there's a setting if you don't know there's a setting to look for or even what it may be called? too often, people have a problem with something and the solution is to try one of a variety of different config settings to rectify the situation. that's a bit like requiring a user of a computer to access the BIOS just to get something to work right.Your loss of constraints and so forth upon closing is because you are not saving all objects with the drawing, there's a config setting for this.
Model tree is configurable.
It all depends on the complexity of the model/assembly. Every software has a pros and cons.I agree with Wogz. I'm currently using both Creo 2 and SW on a daily basis and an equal number of hours per day so I feel I can be justified in giving an opinion and comparing the 2 packages. I continually hear people say what you have said about SW being a middle of the road software package but from what I have seen, everything I can do in Creo I can do in SW and usually with less issues, fewer mouse clicks and quicker. It's stable if done correctly in SW and the 2D drafting in SW is streets ahead. I'd love to see some hard facts on what Creo can do that SW can't.
while I totally understand the point you are making with this, the reality is that many development firms sub out the machining of their tools to any number of suppliers and not all of those suppliers use PTC products or are integrated into the designing firm's CAD database so the updates may not necessarily be seamless even if each firm is using CREO. While the design process as envisioned by PTC is great for a fully integrated and large company, lots of smaller companies can't integrate in the same manner.In Creo the OLD tool path simply updates like a part in assembly mode. Creo Catia and NX have an application for Advanced Assembly / Manufacture etc for example while the mid range modelers do not. ie. Solidworks, Inventor etc...