Hi Pjotr, I have merged you callback test code into the existing osgcallback example, added a new pathway that sets up the callbacks as per your example. To access this pathway you run:
osgcallback --test The output I'm currently getting is: $ osgcallback --test | more Numchildren with updates 4 New Frame Camera event callback - pre traverse0xb2aef0 Camera event callback - post traverse0xb2aef0 test1 test2 test3 test5 test6 Camera update callback - pre traverse0xb2aef0 Camera update callback - post traverse0xb2aef0 New Frame Camera event callback - pre traverse0xb2aef0 Camera event callback - post traverse0xb2aef0 test1 test2 test3 test5 test6 Camera update callback - pre traverse0xb2aef0 Camera update callback - post traverse0xb2aef0 ... I am now embarking on unification of the callbacks as per my earlier discussion in this thread. As I do this I'll look to address the short comings in the current callback handling. 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
