HI Sebastian. On 15 May 2014 11:24, Sebastian Messerschmidt <[email protected]> wrote: > As for the bound issue, I also would accept a break at the cost of > refactoring some lines of code instead of using some artificial construct > unifying the bounds at the cost of one indirection. > OpenSceneGraph has grown very mature over the years and has also grown big. > But don't see any reason why not to break some old interface which can be > fixed with minimal effort on our side.
Have you tried out svn/trunk with latest changes against your application? If it does turn out that the recoding required to work around the Drawable::getBound() change is small enough for enough users than the need for the Bound class is greatly diminished. If we can avoid using it then I'd much prefer not having it. What might appropriate would be to make a dev release with the Bound class in place to enable a bit more testing, then remove it if the cost of re-factoring user code is found to be an acceptable step. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
