Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
When I draft surface its ID is changed after this. What does happen after this? Every operation that I do whith drafted surface now depends on this new surface ID. If I delete draft operation in history automatically some children operation is deleleted. For me it can be prevented by ID conservation. I understand that compatibility with previos versions can be compromised so my proposal is to introduce it as switch option in configuration or manage it directly with kernel. In this way only user mange it. It could be a good thing to keep the same algorythm for all geometry.
Another problem is , after removing from extrude sketch of some segment (arc, line ...) Draft feature (that include surface created with deleted segment) disappear.
In my mind, consistency is more important. One of the things that makes Proe / Creo a robust modeler is the consistent treatment of surface and edge IDs. In this situation I can see an argument both ways, that this is a new surface or that it is a manipulation of an old one.
Creo is not robust enough to be called "robust". It is worst programm that I used in last 15 years. I am trying to improve this program otherwise in June we will pass to other software. Collaborating we can change it.
Interesting, I've worked with Proe / Creo for 17 years and I can bend geometry to my will and repeatedly change and manipulate it. It responds predictably and reliably. I haven't used many other packages, but I have maybe 7 years of SW under my belt and I've never been able to do the same with it. Refeerences don't stick and IDs are too fluid.
Back to the question at hand, my repsonse still stands. Consistancy in geometry ID treatment is more important than optimizing one particular work flow.
I worked with I-Deas (from v.8) and Unigraphics( from ver5). I insist with collaboration. I see an opportunity to do something valuable together.
I have to side with Valery. I've worked with Pro/E for 20 years and robust is the last word I'd use to describe surfacing. All other software packages do it better.
The surface id is one of the biggest sources of failures/frustration. Surface modelling in Pro/E makes the entire model fragile and completely useless if you need to make one small change exactly because the anything that that is downstream of a surface function is at the whim of the id.