[vtkusers] Re: VTK: Mouse Wheel Event

[Charl P. Botha]

On Mon, 2003-08-18 at 12:13, Mathieu Malaterre wrote:
>   > It's not going to be that easy, Mathieu. :)  I just commented out my
> > ZAxisMapping 4 5 option and restarted X... suddenly, the mouse wheel on
> > my MS IntelliEye mouse did NOT work anymore in Mozilla 1.4, OpenOffice
> > 1.0.3, Konqueror 3.1.2, aterm 0.4.2 or evolution 1.2.4.  When I
> > uncommented the line and restarted again, my scroll wheel started
> > working again.
> 
> Obviously yes, this is the way to disable mouse wheel.
> 
> > Conclusion:
> > At least on my system, NONE of these rather popular applications assume
> > that buttons 4 and 5 are the scroll wheel.  
> 
> I never said that. I said that standard option is :
> 
> Option "ZAxisMapping 4 5"

This is what you said:
"I tried some app such as OpenOffice / Mozilla/ Netscape/ Nedit / XEmacs
... *ALL* are mapping wheel event to button 4 and 5. So please if you
know any other app that doesn't make this assumption, please send me.."

They are NOT mapping the wheel event to buttons 4 and 5 and none of
those applications is making the assumption that you claim... they are,
correctly, binding event handlers to Z-Axis motion. You want to bypass
that and bind mouse wheel event handlers directly to button 4 and 5 and
this is the topic of the current debate.

Once again: it's becoming more clear (especially judging by the
application examples that you have mentioned) that a well-behaving X
application should NOT assume that Z-Axis motion has been mapped to
buttons 4 and 5 and react to these buttons as if they were mouse wheel
events. 

I hope I have made myself clear this time. :)

Cheerio,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/