| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Some backends can provide this information for touch devices,
and it can be useful to have, so add this property.
|
|
|
|
|
|
| |
GdkSeat is now the preferred way to deal with input devices and grabs.
https://bugzilla.gnome.org/show_bug.cgi?id=759309
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=759309
|
|
|
|
|
|
|
|
|
|
| |
The way master devices detach from their other master counterpart is
vulnerable to infinite recursion due to the way we first recurse on
the other device before clearing the pointer, this may happen if
that last reference to the other master device is held by the
device->associated field.
https://bugzilla.gnome.org/show_bug.cgi?id=732742
|
|
|
|
|
|
|
| |
Those are not references to other objects, and the device will be mostly
useless if those can't be set again anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=756625
|
|
|
|
| |
This avoids pspec lookup overhead in g_object_notify.
|
|
|
|
|
|
|
| |
These are a construct only properties, expected to be filled in from
platform specific code.
https://bugzilla.gnome.org/show_bug.cgi?id=740758
|
| |
|
|
|
|
|
|
| |
The device and window passed to gdk_device_grab() must be
on the same display, or things are unlikely to work.
Document and assert this.
|
|
|
|
| |
That seems ... counterproductive.
|
|
|
|
|
|
| |
There is no need for a critical warning just because somebody
asked for a property that is not meaningful for the device.
Just document it as not useful for keyboard devices.
|
|
|
|
|
|
|
|
| |
Remove checks for NULL before g_free() and g_clear_object().
Merge check for NULL, freeing of pointer and its setting
to NULL by g_clear_pointer().
https://bugzilla.gnome.org/show_bug.cgi?id=733157
|
|
|
|
|
| |
GdkInputMode doesn't apply to all device types, explain why
and how do these interact.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729983
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729834
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Instead of Return value:
|
|
|
|
|
| |
With all element markup gone, it is time to turn off
sgml mode, and get rid of entities as well.
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
|
|
|
|
| |
Advise against using GDK_POINTER_MOTION_HINT_MASK.
Add pointers to gdk_window_set_event_compression() to the documentation.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
gdk_device_list_slave_devices only makes sense to call on master
devices, yet its g_return_if_fail check made it reject such devices.
Pointed out by monty.
|
|
|
|
| |
This is needed for the win32 master/slave handling code.
|
|
|
|
|
|
|
| |
... and make sure the backends implement it that way.
query_state() return value was ignored in all of GDK and caused crashes
when it failed.
|
| |
|
|
|
|
|
|
| |
_gdk_device_get_axis_use() dates back to pre-sealing, when the
xi2 work began, this remaining can be gone with a public
gdk_device_get_axis_use() function already in place.
|
|
|
|
|
|
|
|
|
|
| |
GDK_NATIVE_WINDOWS was a way to keep some old apps running that did weird
things in gtk2. We should not have to carry this forwards in gtk 3.x.
We do however keep a g_warning() call reminding people of this fact to
ease debugging when they try to port their applications.
https://bugzilla.gnome.org/show_bug.cgi?id=644119
|
|
|
|
|
| |
Reorganize some sections, drop the largely redundant multihead
section, add some more information about multiple backends.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only master devices must modify the associated device to separate
a pointer/keyboard pair, slave devices must only call
_gdk_device_remove_slave().
Fixes bug 639767 - password not accepted in gnome-screensaver dialog,
reported by Frederic Crozat. On VT-switch, the X server removes its
grab on HW devices, the effect on clients is that slave devices
disappear, and these were mistakenly mangling the master device
hierarchy. so gdk_device_get_associated_device() on the client
pointer wouldn't return the paired keyboard anymore.
The final effect is that gtkplug-x11 wasn't setting a keyboard to
its generated events.
|
|
|
|
| |
Documentation bits have been added as well.
|
| |
|
|
|
|
|
| |
Also adds 'Rename to:' annotation to some constructs replacing the
skipped ones.
|
| |
|
| |
|
| |
|
|
|
|
| |
Move a previous vfunc into the only caller.
|
|
|
|
|
| |
Move the only user to call the function directly and copy the called
function over.
|
|
|
|
| |
Previous callers now use _gdk_device_query_state() directly.
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=637895
|
|
|
|
|
| |
warping devices has nothing to do with displays, so putting it there
seems weird.
|
|
|
|
|
| |
The !trusted workaround code is pushed down into the GdkDevice
subclasses, and we use the device vfuncs directly in gdkdisplay.c
|
| |
|