After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573166 - Need docs on how to handle motion events properly
Need docs on how to handle motion events properly
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Documentation
2.15.x
Other All
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: motion-event-tracker
 
 
Reported: 2009-02-25 18:23 UTC by Federico Mena Quintero
Modified: 2018-02-10 03:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Federico Mena Quintero 2009-02-25 18:23:53 UTC 
Bug #573154 indicates that there is widespread confusion and old/wrong code that deals with pointer motion hints, querying pointer positions, and in general implementing press-drag-release for widgets.

We need a chapter in the documentation that explains how all of these work:

- Motion events - do you need all of them?

- Pointer motion hints - how does the X server handle them?  is_hint means "this is the last motion event you'll get until you ask for more".

- gdk_event_query_motions() to request more motion events.

- gdk_device_get_history() for exotic apps.

- You need to use the ButtonRelease event's coordinates!  Don't assume that the last motion event had the final coordinates for your press-drag-release sequence.
Comment 1 Matthias Clasen 2018-02-10 03:37:15 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.