HI Wang Rui, On Tue, Apr 27, 2010 at 10:12 AM, Wang Rui <[email protected]> wrote: > This would cause unexpected behavious because of osgTerrain::Terrain > not derived from osg::CoordinateSystemNode. A static_cast<> will lead > to wrong conversation in that case. If someone would like to record > coordinate system information here, a ADD_USER_SERIALIZER should be > used.
I recently changed osgTerrain::Terrain so it is now subclassed from osg::CoordinateSystemNode, and have updated the serializers and VPB to reflect this. I assumed my changes to the serializers were appropriate. Is there a problem that you are investigating due to this change? > BTW, as there were no replies to my last thread of the osgb > compatibility, I have to fight a lone battle at this stage. :) I'll > try to submit the multi-version controlling functionalities first at > this weekend. Ooops, I thought I had replied... I replied in my head at least ;-) Right now I think the best route would be to put the schema into the binary file itself. This would provide a level for forwards/backwards compatibility and the capability of 3rd party libs parsing the files using the schema as a guide. Cheers, Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
