Oh, just as a supplement, I would say that using serializer revisions is not all-purpose. It could NOT handle backwards compatibility, The old version serializers don't have multi-versions yet, so it will fail if reading a file generated by new OSG distributions. And it also can't handle unknown class wrappers.
Wang Rui 2010/4/23 Wang Rui <[email protected]>: > The example code above means that we have a setWidth()/getWidth() pair > in certain class, which uses an INT parameter in and before 2.9.8, and > changes to use DOUBLE in 3.0.0, and finally changes to FLOAT in latest > versions. Different serializer will be used according to the osgb file > version, and thus keeps the compatibility. > > To evaluate it: > > [ADD] - OK, use a version-specified serializer. > [DEL] - OK, use a version-specified serializer. > [MOD] - OK, use a multi-version serializer. > [CLS] - OK, use a multi-version wrapper. > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
