Ok. I switched to the non-deprecated method I believed was correct, and I'm still seeing a failure, so I need to dig through and see what's going on.
On Fri, Oct 4, 2013 at 2:33 PM, Robert Osfield <robert.osfi...@gmail.com>wrote: > Hi Chris, > > The problem with the computeIntersections() method is that it's ambiguous > w.r.t which window and which camera the x,y coordinates are associated > with, the function has a stab at guessing what you might mean. If you are > seeing a regression then it sounds like this guess might be what is going > amiss. > > W.r.t the regression it would be good to work out what specifically it is > so we can look at fixing it in OSG-3.2.1. The method is deprecated though, > it really tries to hard to be clever and convenient, it's much better for > applications to be more specific such as by using the method that you > explictly pass in which camera to work with. > > Robert. > > > On 4 October 2013 20:13, Chris Hanson <xe...@alphapixel.com> wrote: > >> Some working code of mine stopped working when I upgraded to OSG 3.2 >> from a previous 3.x dev release. >> >> I'm using >> >> bool computeIntersections(float x,float y, const osg::NodePath& nodePath, >> osgUtil::LineSegmentIntersector::Intersections& >> intersections,osg::Node::NodeMask traversalMask = 0xffffffff); >> >> Which is now marked as deprecated but it doesn't really explain why, or >> what to replace it with. I'm not using values from a GUIEventAdapter, so >> I'm assuming I should be using >> >> /** Compute intersections of a ray through the specified camera >> and a specified nodePath's subgraph. */ >> bool computeIntersections(const osg::Camera* camera, >> osgUtil::Intersector::CoordinateFrame cf, float x,float y, const >> osg::NodePath& nodePath, osgUtil::LineSegmentIntersector::Intersections& >> intersections,osg::Node::NodeMask traversalMask = 0xffffffff); >> >> >> with a CoordinateFrame of WINDOW. >> >> Nevertheless, in this case does deprecated mean "broken", or should it >> have continued working? I haven't delved deep down into the deprecated code >> yet, but it looks to me like it's still present and intact. Are there any >> caveats I should know about? >> >> -- >> Chris 'Xenon' Hanson, omo sanza lettere. xe...@alphapixel.com >> http://www.alphapixel.com/ >> Training • Consulting • Contracting >> 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 >> • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL >> Digital Imaging • GIS • GPS • osgEarth • Terrain • Telemetry • >> Cryptography • Digital Audio • LIDAR • Kinect • Embedded • Mobile • >> iPhone/iPad/iOS • Android >> @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) >> 623-PIXL [7495] >> >> _______________________________________________ >> osg-users mailing list >> osg-users@lists.openscenegraph.org >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > -- Chris 'Xenon' Hanson, omo sanza lettere. xe...@alphapixel.com http://www.alphapixel.com/ Training • Consulting • Contracting 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL Digital Imaging • GIS • GPS • osgEarth • Terrain • Telemetry • Cryptography • Digital Audio • LIDAR • Kinect • Embedded • Mobile • iPhone/iPad/iOS • Android @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) 623-PIXL [7495]
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
