Hi Robert 2011/7/18 Robert Osfield <[email protected]>: > There is always an event traversal, like there is always an update > traversal. Both > traversal types have a mechanism for cutting short the traversal of subgraph > if > that subgraph doesn't contain any event and updated callbacks. >
Oh, I think I misunderstand the concept here. Thanks for clarifying it. :-) > > Crappy CEGUI design/implementation decision there. Stuck in the world of SDL > based single threaded/single context applications... > It's of course not safe. That's why I put all the code in drawImplementation() and event handlers, which can avoid thread conflicting using OSG's native threading mechanism. > What you could have is initialize callback that gets called by the CEGUI node > the first time it's traversed in the draw traversal. The initialize > callback could > be lighter weight than the idea od subclassing from a full blown class where > used could get confused about what they need to do. > Yes, draw callback should be a better solution. I'll change my example to use this instead and re-submit it again sometime later.. > > I don't think making the osgWidget library work as a plugin based > scheme would be > sensible. The idea of osgWidget is that it's a native OSG > implementation that has > all the capabilities of the OSG. It's design and implementation falls > a little short > in several areas but that's the idea. > OK. It's good to know the purpose of osgWidgets and I can do something useful later for it. :-) Wang Rui _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
