Hi Farshid, I will have to defer to Wang Rui to get into the nitty gritty bits of the serializers as he's the author of this feature. In general I would say the intention of the serializers is not to crash when handling unrecongized objects. Using 2.9.12 has to be a risk though, the serializers have been improved since then and are more flexible and robust now.
Robert. On 4 October 2012 00:20, Farshid Lashkari <fla...@gmail.com> wrote: > Hi, > > I recently added serialization support for a custom osg::Object derived > class in my application. I saved the object to a osgt and osgb file and > attempted to load it into an older version of my application, which didn't > have serialization support for my custom object yet. > > Loading the osgt file gives me the following warning message: > > InputStream::readObject(): Unsupported wrapper class MyLibrary::MyObject > > This is expected. However, when I attempt to load the osgb file I get the > following output then my application crashes: > > InputStream::readObject(): Unsupported wrapper class MyLibrary::MyObject > InputStream::readObject(): Unsupported wrapper class > > Before I spend time looking into this, I was wondering if it is expected for > the binary loader to crash on unsupported objects? I'm working with osg > 2.9.12, if that makes a difference. > > Cheers, > Farshid > > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
