HI Wang,
Yeah. Default manipulators differ between our test cases. But they booth are
derived from the same base class. I looked at osgviewer you looked at
osganimate.
Wojtek
--------------------------------------------------
From: "Wang Rui" <wangra...@gmail.com>
Sent: Friday, June 18, 2010 4:34 PM
To: "OpenSceneGraph Users" <osg-users@lists.openscenegraph.org>
Subject: Re: [osg-users] Developer release of OSG and VPB imminent,please
test.
Hi Wojciech,
Yes, FlightManipulator also calls centerMousePointer() in its init()
and home() method, which calls requestWarpPointer() internally. The
FlightManipulator and DriverManipulator both bring about the issue.
Cheers,
Wang Rui
2010/6/18 Wojciech Lewandowski <lewandow...@ai.com.pl>:
I hit send too fast. Let me write it again:
Hi J-S,
Just put breakpoints at line where warning is output and in
GraphicsWindowWin32::realizeImplementation(). First is hit before the
second.
So case is straight forward:
FlightManipulator is added to KeySwithcManipulator set as main Viewer
CameraManipulator. When added it calls home() to initialize and home()
calls
requestWarpPointer() to center mouse position.
Its done before Viewer::realize() so the warning is correct.
Question is whether requestWarpPointer() should be called there if its
not
working. GraphicsWindowX11::requestWarpPointer most probably does not
work
too, but it does not display the warning...
Wojtek
PS. Hope it clearer now.
_______________________________________________
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
