Hi Robert,
> This works fine, but... so far I haven't reproduced the picking bug.
> I only have a single display and GPU attached to my machine right now
> so only a single screen. Is it when running dual screen that problems
> occur?
Yes, and to be even more precise, it's in the case when the View is
using slave cameras (so for example when using
osgViewer::View::setUpViewAcrossAllScreens() ). That's why you're not
able to reproduce the problem.
To test it out, I guess you could set up a view to use a single slave
camera. I guess the problem occurs because the view's main camera is not
the one which has the graphics context (hence the traits) and so, the
event state is not set up with the correct extents for the mouse events.
But of course, even better would be to hook up another screen and see it
in the same context as I did - I'm not absolutely sure the "one slave
camera" hack will reproduce the problem.
> I have checked in the modified osgpick example, to run it with
> CompositeViewer simply run:
>
> osgpick --CompositeViewer cow.osg
>
> Once I can reproduce the bug I'll get on properly review your changes.
> Could you test the above to see if you can reproduce the problem.
I'll check it out right now and get back to you.
Thanks,
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
