[JOGL 661] Wrong mouseDragged event send by newt

I'm receiving mouseDragged events instead of mouseMoved using newt (GLWindow) after a drag as ended outside the window.

Here's the steps to reproduce:
 * Press mouse button 1 in the window
 * Drag outside the window
 * Release mouse button 1
 * Move mouse inside the window => mouseDragged received by newt (with getButton returning 1) instead of mouseMoved

So it seem as if newt has never been notified of the mouse release and still caching the mouse pressed states internally (?).
I have to press and release the mouse button to stop sending the mouseDragged events.

This bug is not showing using GLCanvas.

I'm using JOGL 627 on windows 7.
Is anyone noticed this bug yet ?

Hi

On which platform do you reproduce this bug?

On Windows 7 (64 bits)

Please write a bug report. If possible, try to reproduce it on other platforms.

Just tested with Jogl 661 and bug still here.

I'll write a bug report (sorry i was kind of busy last days).

EDIT: Bug 556: mouseDragged events is send instead of mouseMoved by newt. I'll attach a unit test this evening or tomorrow.

On 02/21/2012 06:49 PM, jouvieje [via jogamp] wrote:
>
>
> Just tested with Jogl 661 and bug still here.
>
> I'll write a bug report (sorry i was kind of busy last days).

Thank you - so we are.

Me validating all unit tests against linux-arm ES.

Will pick up the other bugs afterwards as listed on bugzilla.

~Sven

The behavior that has been implemented as a patch to the bug originally
reported in this thread is counterintuitive either. Now NEWT (NewtCanvasAWT)
produces the following events when dragging the mouse so that it exits
 the window, then enters again, and finally release the button.

PRESS, DRAG+, EXIT, (nothing while dragging outside), ENTER, MOVE+, RELEASE

So when the user starts dragging a scrollbar handle for example, when the
mouse exits the window, the dragging operation is interrupted and the user
has to start anew. This is in contrast to what users are used to when dragging,
especially when dragging scrollbar handles.

In contrast, AWT (GLCanvas) produces the following:

PRESS, DRAG+, EXIT, DRAG+ (while outside), ENTER, DRAG+, RELEASE

With this series of events, the dragging continues, regardless the mouse
being either inside or outside of the window.

I further noticed that NEWT (NewtCanvasAWT) reports EXIT twice, when
the user releases the button outside the window after a drag operation,
the RELEASE event is not reported at all:

PRESS, DRAG+, EXIT, (nothing while dragging outside), EXIT

AWT (GLCanvas) correctly reports:

PRESS, DRAG+, EXIT, DRAG+ (while outside), RELEASE

It would be nice, if AWT and NEWT would behave consistently, and that DRAG
would also be reported while dragging outside.

The event listeners I used here are implemented using the newt classes, and
wrapped in AWTMouse/KeyAdapter for the AWT case. I'm under
Ubuntu 12.10 (64bit), latest JGOL release, OpenJDK 7.

You're right about the drag regression (I'm reproducing it too on win 7 x64). The best would be to reopen bug 556 or create a new bugzila bug to track this problem.

Thanks for reproducing this issue!
Yes, I agree, someone (of the maintainers?) should reopen bug 556.