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 495320 - GtkRange does not use gdk_event_request_motions
GtkRange does not use gdk_event_request_motions
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.11.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: motion-event-tracker
 
 
Reported: 2007-11-09 16:13 UTC by Xan Lopez
Modified: 2009-02-25 17:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use-gdk_event_request_motions-for-GtkRange.patch (744 bytes, patch)
2007-11-09 16:33 UTC, Xan Lopez
none Details | Review

Description Xan Lopez 2007-11-09 16:13:15 UTC
As noted in the docs[1], widgets using motion hints should be using gdk_event_request_motions now. The attached patch gets the x, y coordinates from the event instead of doing another roundtrip for them, not sure if that's ok or not...

[1]:http://library.gnome.org/devel/gdk/stable/gdk-Events.html#id2743065
Comment 1 Xan Lopez 2007-11-09 16:33:08 UTC
Created attachment 98826 [details] [review]
Use-gdk_event_request_motions-for-GtkRange.patch

Subject: [PATCH] Use gdk_event_request_motions for GtkRange.

---
 gtk/gtkrange.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
Comment 2 Federico Mena Quintero 2009-02-25 17:29:23 UTC
Makes sense.  Do you need the casts at all, or even the local (x, y) variables?  (I.e. can't you just do range->layout->mouse_x = event->x and use that throughout the rest of the function?)

Go ahead and commit :)
Comment 3 Xan Lopez 2009-02-25 17:39:24 UTC
Thanks, committed in trunk with those changes.