There seems to be no easy way to do this. I read the Serialization page on the wiki. I decided to go ahead and make my data class derive from Node and write a wrapper for it.
On Sat, Mar 26, 2011 at 4:08 PM, Eduardo Poyart <poy...@gmail.com> wrote: > Hello, > > In my application I need to create a file that consists of essentially an > OSGB file plus ancillary data. I have this ancillary data in either an > external binary file or an in-memory buffer. > > I thought I could use osg::Archive to do the archiving and to handle the > OSGB data. If I can write a class that derives from osg::Object (called > something like AncillaryData) and that implements the interfaces to > save/load a memory buffer to an archive, I thought it could fit nicely into > the osg::Archive paradigm. AncillaryData would be able to save/load data > that is opaque to all of OSG and that is handled only by my application. > > Would it be a good way to go? Is it better to do it differently? Any > pointers? > > Thanks > Eduardo > >
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
