[Jung-support] [jung - Open Discussion] RE: JUNG 2 GraphMouse

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4264906
By: andre_rsise

Just to give some update on what I found out about this bug (if indeed it is
a bug):

- Hard-coding the number 72 instead of Event.BUTTON3_MASK is a temporary workaround
that works fine;

- The only JUNG 2 demo that actually uses mouse button 3 is AnnotationsDemo
(this button is used to trigger the annotation popup). However, it does not
use the checkModifiers() method, but instead, in AnnotatingGraphMousePlugin,
the right-click is detected using isPopupTrigger(). That's probably the reason
why this bug has gone unnoticed so far.

I cannot propose a solution since I barely understand the mechanisms used in
AWT and Swing, however I reckon it will require some changes
in edu.uci.ics.jung.visualization.awt.ScreenDevice and also maybe some constants
in edu.uci.ics.jung.visualization.event.Event. For instance, ALT_MASK and META_MASK
have been defined in JUNG's Event class as 4 and 8 respectively, while
java.awt.event.InputEvent defines them as 8 and 4. However, inverting these
does not solve the problem, since anyway the AWT mechanism recognises button3
as META_DOWN, adding an extra bit 1 to the final mask of modifiers. I'm trying
to find out how to differentiate between these two events, so that a few changes
in ScreenDevice could return the right values.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=252062