| |
| |
On 08.01.2014 18:24, Sam wrote:
Hi guys,
<http://www.fltk.org/software.php?VERSION=1.3.2>
Anyone knows the reason why FL_DRAG event is transformed to FL_MOVE
after a FL_RELEASE? Is this a bug?
For example here's the sequence:
Press continuously MB 1 -> FL_PUSH
Move the mouse -> FL_DRAG
Press continuously MB 2 -> FL_PUSH
Move the mouse -> FL_DRAG
Release MB 2 -> FL_RELEASE
Move the mouse -> FL_MOVE
We really have issue with this behavior as it causes many problems when
navigating in our 3D View. This happens on 1.1.X and 1.3.X on both
Windows/Linux, haven't personally checked on OSX.
Not a real answer, but an important question: do you really mean to hold
MB1 while you press and then release MB2 again? This could be the
problem, since FLTK delivers the release event and doesn't "remember"
MB1 status.
Also, in some (most?) cases, FLTK *behavior* is mouse-button-agnostic,
which means that you can drag *either* with MB1 *or* with MB2. This
would explain that behavior, too.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[ Direct Link to Message ] | |
|
| |
