Hello everyone; this is probably a question only a few people could possibly, answer (Robert, Wang), but here goes:
I have created a derived osg::Image class (osgCairo::Image), and this has worked just fine for the last few years. However, I want to add strong serialization support for my nodekits, and I'm finding customizing an Images behavior in the serialization code is quite difficult. Images are treated as special kinds of Objects, so any custom behavior you might add confuses the base serializers, and there doesn't appear to be any way to avoid this. My question is: should the serialization backend be modified to support osg::Image subclasses, or should programmers be encouraged NOT to derive from osg::Image directly and instead create "contains-a" objects instead? _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
