Re: [osg-users] Camera callbacks

HI John, As the Camera has Initial/Pre/Post and FinalDrawCallbacks having add/remove/getNum/get methods rather than just set/get will mean a lot of extra new methods expanding an already large API. To avoid a big expansion in the API it would probably be best to push the list of callbacks onto Dr

Re: [osg-users] Camera callbacks

Hi Robert, > Providing similar support for Camera::DrawCallbacks would be possible, > there isn't the same imperative for controlling traversal, but it'd > keep the public Camera API simple - it's complicated enough as it is > so am reluctant to add further API to it. Sorry, I am not native Engli

Re: [osg-users] Camera callbacks

Hi John, Original Node callbacks didn't support multiple callbacks, but I worked out that I could add the functionality relatively non-intrusively by nesting callbacks. The key advantage with nesting is that it enables a callback retain data on the stack within the local scope of the callback - wh

[osg-users] Camera callbacks

Hi, I very like the capability of osg::Node to register any number of update, event and cull callbacks. This allows for a nice modular approach with each module registering callbacks for anything they wish without disturbing others. I came to a problem that Camera can register just one Initial-