summaryrefslogtreecommitdiff
path: root/clutter
diff options
context:
space:
mode:
authorCarlos Garnacho <carlosg@gnome.org>2018-04-20 12:43:22 +0200
committerCarlos Garnacho <carlosg@gnome.org>2018-04-22 12:14:37 +0200
commitc80e2c9ae5b2c0f3df1ae4cca9c4f3e02ce034d8 (patch)
treede313854b8d1c14fb7c000283871d20d80d72607 /clutter
parentd3d5eb8e1b3b07a38860a9dbe58c601392e0ad75 (diff)
downloadmutter-c80e2c9ae5b2c0f3df1ae4cca9c4f3e02ce034d8.tar.gz
clutter: Set slave=master in IM forwarded key events
The fix is twofold. On one hand, it makes sense not to relate IM (nor any other) generated events to a HW device. On the other hand, if we are unfortunate that an IM event is in flight when we are switching to another TTY, it may arrive at a time when the source device is no longer existent.
Diffstat (limited to 'clutter')
-rw-r--r--clutter/clutter/clutter-input-method.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/clutter/clutter/clutter-input-method.c b/clutter/clutter/clutter-input-method.c
index e90bdfcf6..11d726d7b 100644
--- a/clutter/clutter/clutter-input-method.c
+++ b/clutter/clutter/clutter-input-method.c
@@ -353,6 +353,7 @@ clutter_input_method_notify_key_event (ClutterInputMethod *im,
copy = clutter_event_copy (event);
clutter_event_set_flags (copy, clutter_event_get_flags (event) |
CLUTTER_EVENT_FLAG_INPUT_METHOD);
+ clutter_event_set_source_device (copy, clutter_event_get_device (copy));
clutter_event_put (copy);
clutter_event_free (copy);
}