On 01/17/2014 11:21 PM, Stefan Salewski wrote:
On Fri, 2014-01-17 at 17:11 -0500, Jasper St. Pierre wrote:
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
On Fri, 2014-01-17 at 17:26 -0500, Jasper St. Pierre wrote:
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.
I sent a message to the Ruby-Gnome2
If you have a keyboard device, you can use
gdk_device_get_associated_device() to return the paired mouse device.
On Fri, Jan 17, 2014 at 4:26 PM, Stefan Salewski m...@ssalewski.de wrote:
I recently ported a GTK2 application to GTK3
(http://www.ssalewski.de/PetEd.html.en)
I had some working
I recently ported a GTK2 application to GTK3
(http://www.ssalewski.de/PetEd.html.en)
I had some working Ruby code like this for GTK2:
def distribute_events(pda, event)
if event.event_type == Gdk::Event::Type::KEY_PRESS
px, py = pda.get_user_coordinates(*pda.pointer)
else
px, py =
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.
On Fri, Jan 17, 2014 at 5:05 PM, Stefan Salewski
On Fri, 2014-01-17 at 16:38 -0500, Jasper St. Pierre wrote:
If you have a keyboard device, you can use
gdk_device_get_associated_device() to return the paired mouse device.
Fine -- but currently I have only a keyboard event as described in
On Fri, 2014-01-17 at 17:11 -0500, Jasper St. Pierre wrote:
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
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 m...@ssalewski.de wrote:
On Fri, 2014-01-17 at
On Fri, 2014-01-17 at 17:18 -0500, Paul Davis wrote:
you can track where the mouse is with enter/leave events, and there
are
often good reasons for wanting to do that anyway.
That should not work well for CAD applications.
We have a large drawing area, where we draw objects using cairo
On Fri, Jan 17, 2014 at 5:29 PM, Stefan Salewski m...@ssalewski.de wrote:
On Fri, 2014-01-17 at 17:18 -0500, Paul Davis wrote:
you can track where the mouse is with enter/leave events, and there
are
often good reasons for wanting to do that anyway.
That should not work well for CAD
On Fri, 2014-01-17 at 17:11 -0500, Jasper St. Pierre wrote:
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
Deprecated methods should not raise an exception. Deprecated methods
shouldn't stop working because they're deprecated.
On Fri, Jan 17, 2014 at 7:11 PM, Stefan Salewski m...@ssalewski.de wrote:
On Fri, 2014-01-17 at 17:11 -0500, Jasper St. Pierre wrote:
Yeah. This is to maintain ABI
On Fri, 2014-01-17 at 19:19 -0500, Jasper St. Pierre wrote:
Deprecated methods should not raise an exception. Deprecated methods
shouldn't stop working because they're deprecated.
Yes, that was my feeling also, and for most deprecated methods in GTK3 I
got only warnings. But
13 matches
Mail list logo
