Hi David, I've just merged and checked into svn/trunk your changes that add usage of META_OSGMANIPULATOR, but have held back from merging the _depth changes as I don't yet understand these changes.
You mention in your email about placing the dragger geometry into a separate bin, but the PointInfo code only contains a depth, and I can't work out how they are related. The general approach to solving this problem seems awkward, and can't help feel that perhaps the dragger intersection code itself would be better off being tweaked so that it ignores non dragger geometry automatically. Robert. On Wed, Mar 4, 2009 at 9:46 PM, David Callu <[email protected]> wrote: > Hi Robert, > > osgManipulator Object have not META_Object macro call in class definition. > I add META_OSGMANIPULATOR_Object macro which define className, libraryName, > isSameKindAs methods. > Clone method is not appropriate for osgManipulator Object. > > > > Problem: When I use osgManipulator::Dragger, geometry dragger is partially > hide by dragged geometry. > To fix this, I render the Dragger geometry in different RenderBin. But to > Pick the dragger, I need to > search in the IntersectionList if I pick a dragger geometry. Just check the > first Intersection is not sufficient. > > I introduce 'int _depth' variable in osgManipulator::PointerInfo. We can now > define how many Intersection is > checked in the IntersectionList to find a dragger based class. > > I join osgManipulator_patch.tgz > > Cheer > David Callu > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
