Hi Pjotr, Thanks for the example. Would it be OK for me to use/adapt it as part of the OpenSceneGraph/examples set so it could be used as a unit tests?
I have been thinking about the overlap between Node and Drawable Update/Event/CullCallbacks and one idea that currently appeals to me is to have a Node::setUpdateCallback(Object*) method that you can assign either a NodeCallback or a Drawable::UpdateCallback, with the internal implementations that call the callback doing a dynamic_cast<> or similar to determine which type of callback it it. This route also opens the door to supporting osg::CallbackObjects alongside NodeCallback/DrawbleCallbacks. This interest in this would be that it'd open the door to scripting integration with these standard callback entry points. I'm not quite sure how this might all work in practice, the difficult part is making sure we retain backwards compatibility as far as possible without compromising the design, unifying stuff and making it more flexible sounds quite appealing so probably worth the extra effort. Robert. On 21 May 2014 10:51, Pjotr Svetachov <[email protected]> wrote: > I made a little testfile with all the permutations of nodes/drawables and > updatecallbacks could come up with. The last two would never come up in old > code and maybe only by accident in new code. > > It adds 7 update callbacks. > For me only 4 are called and the parent group says that only 3 children > require update traversal. > > Hope this helps. > > Cheers, > Pjotr > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=59506#59506 > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
