> > > 1. Develop your own wxViewer3d class by copy/modify the wxDisplay.py > script. It's a *bad* idea since this script is part of pythonOCC and > this should be confusing. If you really want to proceed that way, use > another module name, for instance SlicerDisplay.py or DaveDisplay.py, > but not wxDisplay.py. >
Yes, i'm already learning this was a bad decision-- though in my defense more out of ignorance than anything else. In next versions i'll fix this. > > 2. Overload the wxViewer3d class that come with pythonOCC. > > from OCC.Display.wxDisplay import wxViewer3d > class myViewer(wxViewer3d): > etc. > > In the latest svn rev., I modified the structure of the wxViewer* > classes. I created a wxBaseViewer3d that can be used to build customized > displays: > from OCC.Display.wxDisplay import wxBaseViewer3d > class myViewer(wxBaseViewer3d): > etc. > This seems like the way i'd like to go. I presume that the base classes are not yet available in the wo0.2 release? I'd like to say with things that will run against a version that has a stable installer-- since many people who use my app will not be on the 'bleeding edge'. When is the next 'main release' planned?
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
