THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#1136 - Titlebar: Strange bug when trying to move a window
User who did this - Uli Schlachter (psychon)
Reason for closing: Fixed
Additional comments about closing: commit
efd243b6d70b9c549c184c3c0b84c481453411e0
Author: Uli Schlachter <psyc...@znc.in>
Date: Sun Oct 6 10:34:37 2013 +0200
event: Handle MotionNotify before ButtonPress/Release (FS#1136)
The above-mentioned bug report says that a window cannot be moved via its
titlebar if you move the move quickly while clicking.
The reason for this was awesome's "event compression": We don't handle all
MotionNotify events, because they can come in big quantities. Instead, we
only
want to handle the latest one and ignore all earlier ones (the mouse isn't
in
that position anymore anyway).
The problem now appears if a MotionNotify is moved across a ButtonPress
event
and the ButtonPress is what should cause the window to be moved. Awesome
first
handles the ButtonPress event normally and starts grabbing mouse input.
Then,
our event loop feeds us with an old MotionNotify event in which the button
was
not pressed yet. The code for moving clients gets a motion event in which no
mouse button is pressed, concludes that the move is done and ungrabs the
mouse
again, even though the button is still physically pressed.
Fix this by making sure that MotionNotify events are never moved across
ButtonPress or ButtonRelease events. We already did this for EnterNotify and
LeaveNotify events for similar reasons.
Signed-off-by: Uli Schlachter <psyc...@znc.in>
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1136
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
