Hi Glenn, I don't have any plans for the 3.4 to make further changes to osg::Geometry. The osg::Geometry::set*Binding() methods are officially deprecated but I'm not in a hurry to remove them. It's best practice to use the osg::Array::setBinding() method or passing in the binding when you do a set*Array(), but for ease of backward compatibility for users I feel the the old set*Binding() methods at least allow users to still build against older versions of the OSG without too much difficulty.
I also won't be removing the set*Binding() methods without discussion with the community of when and how best to do it. I'm open to suggestions, but for now happy with things as they are so won't be pushing removal. Robert. On 4 October 2013 18:40, Glenn Waldron <[email protected]> wrote: > Robert, > > I want to make sure I'm clear on your intentions for the osg::Geometry > API, specifically regarding the deprecated set*Binding functions. > > The code comments say you plan to remove them entirely in a future > version; is that still your intention, or do you just plan to remove the > #define that includes them in by default and let the developer decide? Is > the topic up for discussion? > > Thanks much for clarifying. This is going to have a significant impact on > how we proceed with upcoming osgEarth version releases. > > Glenn Waldron / @glennwaldron > > _______________________________________________ > 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
