Hi Robert, both double call and crash fixed on my side as well.
Now that one can safely implement a callback by deriving directly from osg::Callback, I think most users should go that way for their new code. If that's the case, the not-very-intuitive path of implementing operator() rather than run() in the NodeCallback should be a minor issue. Maybe a note in the comments suggesting to derive from osg::Callback rather than the legacy classes could be worth it? Thank you, Riccardo On Thu, Oct 6, 2016 at 7:30 PM, Robert Osfield <[email protected]> wrote: > Hi Riccardo, > > I have found the cause of the double call, fixed it and have now > checked in this fix and the other fixes to event callback handling. > Changes checked into OSG git master. > > Could you test them out on your application to make sure that things > are now behaving themselves. > > Thanks, > Robert > _______________________________________________ > 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
