From a8c8df6ee8fa62aca6cbb17d69a6ff9f1bd55fa4 Mon Sep 17 00:00:00 2001 From: Giovanni Campagna Date: Sun, 3 Feb 2013 16:43:54 +0100 Subject: [PATCH] StImText: don't translate keyboard state again Clutter translates keyboard state internally, and clears the lock bits from modifier state, so translating again results in the wrong keysym. Given that Clutter already gives us a fine keysym, we don't need this. https://bugzilla.gnome.org/show_bug.cgi?id=692586 --- src/st/st-im-text.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/st/st-im-text.c b/src/st/st-im-text.c index 6419c6661..9f542ab37 100644 --- a/src/st/st-im-text.c +++ b/src/st/st-im-text.c @@ -316,10 +316,6 @@ key_event_to_gdk (ClutterKeyEvent *event_clutter) * doesn't support XKB; we'll just end up with group == 0 */ event_gdk->group = XkbGroupForCoreState (event_gdk->state); - gdk_keymap_translate_keyboard_state (keymap, event_gdk->hardware_keycode, - event_gdk->state, event_gdk->group, - &event_gdk->keyval, NULL, NULL, NULL); - if (event_clutter->unicode_value) { /* This is not particularly close to what GDK does - event_gdk->string