Posted by rhatcher on Oct 10, 2012; 12:02pm
URL: https://forum.jogamp.org/Mouse-Button-Modifiers-Lost-In-Newt-mouseDragged-Events-tp4026456p4026464.html

Heh.  Your response made me laugh.  Have some coffee!

The bottom line summary is that the NEWT events aren't telling the whole story about the mouse button state during mouseDragged and probably mouseMoved too, at least with JDK 7u7.  The reason appears to be because a) AWT's getButton() method doesn't provide button info for those events (who knows why), and b) NEWT's translation of modifier flags only picks up two of the buttons by happenstance due to their association with the META and ALT masks.

It is odd that this hasn't been seen before, so perhaps it works differently in older versions of the AWT.

We do our own builds routinely and will of course be happy to submit a change for consideration.  The biggest issue we have is that we aren't set up to test these changes across a wide variety of platforms; really just Linux, and a relatively old version at that.  So... you will need to consider any such changes as "suggestions" much like we did the X11 screen issue a few weeks ago and adjust as you see fit.

A couple questions/clarifications:

1) So for now the process for submission of patches for less familiar persons such as our group will be to attach modified code in Bugzilla and avoid direct commits.  Obviously it is important to maintain some order in the code base and avoid a free-for-all, so somebody on your end still needs to approve such changes.

2) In your ant build infrastructure, is there a magic property somewhere that will turn on debug info (locals, line numbers, etc) across the board for gluegen, jogl, and joal?  Seems like the last time I was through some of this code in the debugger some of that info was missing.