isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2025-02-04 07:34:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Don't pass handled key events to GTK+

Browse Source 
If we handle a key event then passing it to GTK+ as well can only
cause confusion. Normally GTK+ would do nothing with a key event for
some window it doesn't know about, but plugins might be doing more
things with the GTK+ event queue.

https://bugzilla.gnome.org/show_bug.cgi?id=642426
This commit is contained in:
Owen W. Taylor 2011-02-15 18:17:25 -05:00
parent 6e23b0af3b
commit e7d336ab0e
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/core/display.c
View File

@ -1746,9 +1746,10 @@ event_callback (XEvent *event,
* we can get into a confused state. So if a keybinding is * we can get into a confused state. So if a keybinding is
* handled (because it's one of our hot-keys, or because we are * handled (because it's one of our hot-keys, or because we are
* in a keyboard-grabbed mode like moving a window, we don't * in a keyboard-grabbed mode like moving a window, we don't
* want to pass the key event to the compositor at all. * want to pass the key event to the compositor or GTK+ at all.
*/ */
bypass_compositor = meta_display_process_key_event (display, window, event); if (meta_display_process_key_event (display, window, event))
filter_out_event = bypass_compositor = TRUE;
break; break;
case ButtonPress: case ButtonPress:
if (display->grab_op == META_GRAB_OP_COMPOSITOR) if (display->grab_op == META_GRAB_OP_COMPOSITOR)