I'm feeling very pleased. After a great deal of head-scratching, I think I've figured out Topological Naming (OCAF / TNaming). I've modified my Feature Tree Demo to include a Chamfer tool. The chamfer tool needs to track the chamfered edge through modifications to it's input topology. For this, you need Topological Naming and Selection and hence OCAF in all it's glory (gory?).
I've now put all my testing code up on google.code, so if you want to take a look at this, see the files under https://pythonocc-examples.googlecode.com/svn/trunk/src/InteractiveFeatureTree/ Unfortunately, Topological Naming requires that every bit generated or modified topology (including all subshapes) be stored in the OCAF data framework. This adds a lot of extra verbosity to the code. The end result is that you can the input structure to the Chamfer operation (the block, sphere and BOP) and the chamfered edge remains valid. If you edit the input such that the chamfered edge is deleted entirely, things breakdown. I need to debug this case in more detail. Anyway, this gives a basic demo of the principle. cheers, Bryan _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
