Hi All, My opinions about what to do in about osg::Geometry and the old deprecated functionality is continuing to evolve. I'm starting to feel that have an osg::GeometryDeprecated is going to be awkward to maintain and for end users, while the new cleaned up osg::Geometry is clearly much better from an internal implementation and performance point of view it might be best in the short term to maintain support for the old deprecated functionality.
For the old deprecated usage, while keep the clean fast path only implementation I am think about having an internal osg::Geometry that is generated from the parent osg::Geometry that is fully fast path complient and automatically generated from the parent osg::Geometry's data. This fallback could be optionally compiled out, as could the public API for the old deprecated functionality. One could also at runtime disable the fallback and possible emit an std::exception to help users who want to migrate across. Thoughts? Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
