Emmanuele Bassi authored Nov 07, 2014 and Matthias Clasen committed Nov 08, 2014

The current way of exposing GDK API that should be considered internal
to GTK+ is to append a 'libgtk_only' suffix to the function name; this
is not really safe.

GLib has been using a slightly different approach: a private table of
function pointers, and a macro that allows accessing the desired symbol
inside that vtable.

We can copy the approach, and deprecate the 'libgtk_only' symbols in
lieu of outright removal.

https://bugzilla.gnome.org/show_bug.cgi?id=739781

Owen W. Taylor authored Mar 12, 2014 and Matthias Clasen committed Mar 12, 2014

Add gdk_device_get_last_event_window(), and use to implement the window
tracking we need for synthesizing crossing events for sensitivity changes
and gtk grabs, rather than keeping the information in qdata and updating
it based when GTK+ gets events.

https://bugzilla.gnome.org/show_bug.cgi?id=726187

https://wiki.gnome.org/Design/OS/Typography

We've long had double precision mouse coordinates on wayland (e.g.
when rotating a window) but with the new scaling we even have it on
X (and, its also in Xinput2), so convert all the internal mouse/device
position getters to use doubles and add new accessors for the
public APIs that take doubles instead of ints.

This is in preparation to modernizing our handing
of exported symbols.

gcc has optimizations for include guards that only work
if they are outermost in the the header.
https://bugzilla.gnome.org/show_bug.cgi?id=689810

We don't have any API using the GdkExtensionMode enumeration, so
no point in carrying it in the headers.

We introduce GDK_SOURCE_TOUCHSCREEN and GDK_SOURCE_TOUCHPAD
for direct and indirect touch devices, respecively. These
correspond to XIDirectTouch and XIDependentTouch in XI2.

The source of a device is not changeable.

It's now called gdk_device_get_window_at_position(). It doesn't make
sense to keep device-specific API part of the display.

The API was not display-specific, but belonged to the device. Also, we
didn't find a user of the modifier mask, so we dropped it.

And, since we've decided to keep the structs private, there is
no point in having the standard GObject clas macros anymore either.

Benjamin Otte authored Dec 20, 2010 and Matthias Clasen committed Dec 21, 2010

warping devices has nothing to do with displays, so putting it there
seems weird.

Once its hidden, we can kill the GdkDevicePrivate struct too.

The xi2 device manager now handles slaves being detached and/or
attached to a master.

gdk_device_list_slaves() has been added so it is possible to
know how slaves relate with masters. The other backends (X11 and not)
don't neeed to to anything special here since their hierarchy is
fully flat.

move GdkDeviceKey to gdkdevice.c because it's still used there, remove
GdkDeviceAxis entirely.

"n_events" went back from guint to gint.