On Tue, 2006-08-29 at 02:29 -0300, bulia byak wrote:
Well, this one _always_ calls gdk_window_get_pointer, on each motion event, which kinda defeats the purpose, doesn't it?
No, that's how you're supposed to do it. Remember that when motion hints are enabled, you're not getting an event for every individual motion event, but rather a single event for every group of motion events between calls to gtk_window_get_pointer.
That way, no matter how many real events arrive while you're busy updating the screen, there will only be ever be a maximum of one motion hint event waiting for you to process when you finally return to the event loop.
See the description of GDK_POINTER_MOTION_HINT_MASK below http://developer.gnome.org/doc/API/2.0/gdk/gdk-Events.html#GdkEventMask
-mental