Robert, Agreed, we did this out of temporary necessity; the right thing moving forward is for osgEarth to check the OSG version when creating/registering the osg::TextureBuffer serializer.
Glenn Waldron On Mon, Mar 27, 2017 at 3:27 AM, Robert Osfield <[email protected]> wrote: > Hi Li, > > On 26 March 2017 at 23:26, Li Chi <[email protected]> wrote: > > Sorry for bothering, I found the cause of the warning > "ObjectWrapperManager::addWrapper(): 'osg::TextureBuffer' already exists. > ". > > > > Because osgEarth already has the osg::TextureBuffer serializer in > TextureBufferSerializer.cpp file, so when use osg and osgEarth together, > the warning message printed out. > > This might be a bit awkward to resolve, it shouldn't really be > osgEarth's place to implement serializers for core OSG classes because > it has the potential of overlapping with core OSG implementations. If > osgEarth has a stable release this is in then we'll need to come up > with some workaround - either making osgDB resilient to these > conflicts or having osgEarth check OSG versions and not implement > stuff, however, this is fraught with potential problems as the order > and parameters serialized out could easily be different. > > Robert. > _______________________________________________ > 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
