wayland: make key event log more explicit
authorOlivier Fourdan <ofourdan@redhat.com>
Wed, 26 Apr 2017 13:35:42 +0000 (15:35 +0200)
committerOlivier Fourdan <ofourdan@redhat.com>
Fri, 28 Apr 2017 11:08:37 +0000 (13:08 +0200)
With Wayland, GDK_DEBUG=events would log key events but not explicitly
state whether the event is a key press or release, or if it's
originating from a key repeat.

Add some more verbosity to make sure these informations are logged on
key delivery when GDK_DEBUG is set.

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

gdk/wayland/gdkdevice-wayland.c

index 947ef4453084eff5c4c5e4003da21c0914f3d19f..80e6d36ac4a503af5076e2849d1c0c7dc8c2f549 100644 (file)
@@ -2125,10 +2125,13 @@ deliver_key_event (GdkWaylandSeat *seat,
   _gdk_wayland_display_deliver_event (seat->display, event);
 
   GDK_NOTE (EVENTS,
-            g_message ("keyboard event, code %d, sym %d, "
-                       "string %s, mods 0x%x",
+            g_message ("keyboard %s event%s, code %d, sym %d, "
+                       "string %s, mods 0x%x, with %i key%s pressed",
+                       (state ? "press" : "release"),
+                       (from_key_repeat ? " (repeat)" : ""),
                        event->key.hardware_keycode, event->key.keyval,
-                       event->key.string, event->key.state));
+                       event->key.string, event->key.state,
+                       seat->nkeys, (seat->nkeys > 1 ? "s" : "")));
 
   if (!xkb_keymap_key_repeats (xkb_keymap, key))
     return;