Hi Jeremy, I would have though it would be appropriate to support subclassing of osg::Image in the serializers. I'll defer to Rui to answer the specifics of how we might go about this.
Robert. On Tue, Aug 16, 2011 at 5:42 PM, Jeremy Moles <[email protected]> wrote: > 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 > [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
