Sure you can adapt and use it as an example. As you can't have a Drawable::UpdateCallback on a osg::Node it sounds weird that Node::setUpdateCallback(Object*) can accept a Drawable::UpdateCallback. What do you do when someone passes a Drawable::UpdateCallback to a Node? I rather have an compile error than a error/warning at runtime. This is what the code does now, except that the syntax to assign a normal UpdateCallback to a drawable is weird which might prevent people from using/discovering it. I think that if you make Node::UpdateCallback virtual this should be resolved, right?
Also whats the point of a Drawable::Update/Event/CullCallback now, should't they be deprecated now that a Drawable is a Node and can use the Node's callbacks? Cheers, Pjotr ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=59524#59524 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
