MantisBT - VTK
View Issue Details
0010088VTK(No Category)public2009-12-31 12:182013-04-05 20:14
David Cole 
David Cole 
normalminoralways
closedfixed 
 
 
0010088: GetEventPosition coordinates are incorrect on Windows builds when MouseWheelForwardEvent and MouseWheelBackwardEvent are invoked
GetEventPosition coordinates are incorrect on Windows builds when MouseWheelForwardEvent and MouseWheelBackwardEvent are invoked.

The WM_MOUSEWHEEL handling code in vtkWin32RenderWindowInteractor.cxx does not do a "::ScreenToClient" call as it should... Therefore GetEventPosition values are reported in screen coordinates rather than client window coordinates.

GetEventPosition values should all be in the same (client window) coordinate space regardless of which event is being invoked.
No tags attached.
Issue History
2009-12-31 12:18David ColeNew Issue
2009-12-31 12:18David ColeStatusbacklog => tabled
2009-12-31 12:18David ColeAssigned To => David Cole
2009-12-31 12:33David ColeNote Added: 0019018
2009-12-31 12:33David ColeStatustabled => @80@
2009-12-31 12:33David ColeResolutionopen => fixed
2011-01-13 17:00Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00Source_changeset_attached => VTK master 020ef709
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2013-04-05 20:14Berk GeveciStatuscustomer review => closed

Notes
(0019018)
David Cole   
2009-12-31 12:33   
Fixed in CVS HEAD of VTK.

cvs commit -m "BUG: Fix issue 0010088 - call ScreenToClient on the position values that come into the WM_MOUSEWHEEL events on Windows. This ensures the render window interactor always returns values in the client window coordinate space from GetEventPosition."

/cvsroot/VTK/VTK/Rendering/vtkWin32RenderWindowInteractor.cxx,v <-- vtkWin32RenderWindowInteractor.cxx
new revision: 1.108; previous revision: 1.107