Posted by Sven Gothel on Oct 24, 2011; 6:41pm
URL: https://forum.jogamp.org/JOGL-Ardor3D-tp3434168p3449110.html

On Monday, October 24, 2011 08:31:26 PM gouessej [via jogamp] wrote:
>
> Hi
>
> This bug prevents me from porting the pre-beta version of TUER to JOGL 2.0:
> https://jogamp.org/bugzilla/show_bug.cgi?id=413
> https://jogamp.org/bugzilla/show_bug.cgi?id=413 
>
> A mouse pressed event with MouseEvent.BUTTON4 is generated instead of a
> mouse wheel event. Sven, do you know how to fix this bug?

No, but it rings a bell now.

While still @ Sun, we had a 'discussion' whether to use a dedicated 'wheel'
event or just representing them as another 'button'.

Well, I favored the latter since it's a more generic approach,
plus we really cannot tell what-else game-pads may have.
Technically it's a button, hence a pass-through button representation
is IMHO best. For sure I can be convinced otherwise with good (tech.) arguments.

Maybe we can make a checklist here how the wheel is
represented on the native platforms:

Android: None
X11: Usually button4 and button5
Windows: ?
OSX: ?

If they all use a button representation, I guess it's best to remove the 'wheel' ID.

Let me copy paste this email to the bugzilla entry,
so we can continue it's discussion there (where it belongs IMHO).

Cheers, Sven