From Tatsuhiro Nishioka, "I found a bug in GraphicsWindowCarbon. GraphicsWindowCarbon::requestWarpPointer() places the mouse pointer in a (global?) display coordination, but it must be in a local window coordination. This problem is critical because the mouse cursor can go off a window especially when you place the window on the secondary screen.
From Tatsuhiro Nishioka, "I found a bug in GraphicsWindowCarbon.
GraphicsWindowCarbon::requestWarpPointer() places the mouse pointer in a (global?) display coordination, but it must be in a local window coordination. This problem is critical because the mouse cursor can go off a window especially when you place the window on the secondary screen.

Attached is the file to fix this problem.

I tested this modified file with the following situations (on FlightGear) and all works fine.
- two windows on two screens (each has one window).
- two windows on two screens (secondary screen has all windows).
- two windows on two screens (primary screen has all windows).

In all scenarios, warp requests (by right-click the mouse) successfully moves the mouse pointer to the center of the main window,
and it is what it's supposed to be in the flightgear."


ghub/osg,koshman86/osg,stmh/osg,ghub/osg,XiaoCC/osg,XiaoCC/osg,stmh/osg,omega-hub/osg,omega-hub/osg,XiaoCC/osg,artoolkit/osg,koshman86/osg,omega-hub/osg,XiaoCC/osg,koshman86/osg,koshman86/osg,artoolkit/osg,XiaoCC/osg,omega-hub/osg,artoolkit/osg,stmh/osg,ghub/osg,ntoand/osg,ghub/osg,stmh/osg,artoolkit/osg,ntoand/osg,ntoand/osg,stmh/osg,ntoand/osg