It doesn't seem like there's anything wrong with using the deprecated methods, then. File a bug with the Ruby GTK3 bindings, and continue using window.get_pointer(); for now would be my suggestion.
On Fri, Jan 17, 2014 at 5:21 PM, Stefan Salewski <mail@xxxxxxxxxxxx> wrote:
On Fri, 2014-01-17 at 17:11 -0500, Jasper St. Pierre wrote:I guess current GTK3 Ruby bindings do not allow event_get_device() for
> Yeah. This is to maintain ABI compatibility. Technically, events have
> private internal data, and you can use gdk_event_get_device(); to get
> the
> keyboard device for a key event.
>
> This isn't documented very well; we should perhaps clean this up.
keyboard events :-(
Maybe
https://developer.gnome.org/gtk3/stable/GtkWindow.html#gtk-window-get-screen
followed by
https://developer.gnome.org/gdk2/stable/GdkScreen.html#gdk-screen-get-display
followed by
https://developer.gnome.org/gdk2/stable/GdkDisplay.html#gdk-display-get-pointer
may give me the current mouse coordinates of pointer in my drawing area?
Best regards,
Stefan Salewski
--
Jasper
_______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
