Hi, Does OpenCascade support "Feature Trees"? I.e. If I create a Shape via a sequence of operations e.g.
>BRepPrimAPI_MakeBox -> BRepFeat_CylindericalHole --> BRepFilletAPI_MakeChamfer If I then want to go back and edit the parameters of, say, my original box, do I need to create new BRepBuildAPI_MakeShape objects and recreate a totally new Shape to replace the old one, or can I somehow edit the existing MakeShape objects and have my shape update itself "magically"? I'm coming from a background with VTK (www.vtk.org) where you set up a data visualisation "pipeline". Pipeline objects evaluate their output (data objects) lazily (i.e. on demand). If you change the parameters of a pipeline object, the changes automatically propagate down the pipeline when you render a scene. I'm wondering if OpenCascade can do anything similar. A related question is whether there's any permantent relationship or link between a TopoDS Shape object and the BRepBuilderAPI_MakeShape objects which created it? Are the MakeShape objects reuseable? I know OCAF can facilitate undo/redo but this is not quite what I want. OK, sorry this question has been a bit vaugue. Any opinions on this I'd most appreciate. Bryan _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
