[gtk+] gdk: Explain the relation between device type and mode
- From: Carlos Garnacho <carlosg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gtk+] gdk: Explain the relation between device type and mode
- Date: Mon, 21 Jul 2014 20:39:01 +0000 (UTC)
commit 7995cd59d0ee4a5a9a8e3d1a8756da0f42e4b22d
Author: Carlos Garnacho <carlosg gnome org>
Date: Mon Jul 21 21:17:31 2014 +0200
gdk: Explain the relation between device type and mode
GdkInputMode doesn't apply to all device types, explain why
and how do these interact.
gdk/gdkdevice.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
---
diff --git a/gdk/gdkdevice.c b/gdk/gdkdevice.c
index 544b681..e784dfa 100644
--- a/gdk/gdkdevice.c
+++ b/gdk/gdkdevice.c
@@ -748,6 +748,10 @@ gdk_device_get_mode (GdkDevice *device)
* device is active and whether the device’s range is mapped to the
* entire screen or to a single window.
*
+ * Note: This is only meaningful for floating devices, master devices (and
+ * slaves connected to these) drive the pointer cursor, which is not limited
+ * by the input mode.
+ *
* Returns: %TRUE if the mode was successfully changed.
**/
gboolean
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]