gtk2/gdk/mir
Andreas Pokorny 056ddf2567 Fix execution of dialog
When a dialog is created, the mir event source is already executed on the
call stack. So without the recurse flag it will not be run in the main loop
used for the dialog.

https://bugzilla.gnome.org/show_bug.cgi?id=768138
2016-08-11 12:23:38 -04:00
..
gdkmir-debug.c mir: fix warnings 2016-02-24 13:24:14 -05:00
gdkmir-private.h Rework window construction - only recreate surface when necessary 2016-08-10 13:36:38 -04:00
gdkmir.h mir: Add C++ guards 2016-02-11 12:01:39 +00:00
gdkmircursor.c mir: rework cursors a bit 2014-11-06 16:18:53 -05:00
gdkmirdevicemanager.c gdk: remove the core_pointer field from GdkDisplay 2016-02-29 14:15:04 +01:00
gdkmirdisplay.c Rework window construction - only recreate surface when necessary 2016-08-10 13:36:38 -04:00
gdkmireventsource.c Fix execution of dialog 2016-08-11 12:23:38 -04:00
gdkmirglcontext.c Remove GdkGLProfile 2015-02-12 17:51:31 +00:00
gdkmirkeyboard.c Gdk: add an experimental backend for mir 2014-10-22 11:17:15 -05:00
gdkmirkeymap.c gdkkeys: Add support to _get_scroll_lock_state() 2015-04-27 20:07:52 -03:00
gdkmirpointer.c mir: end the current grab on ungrab 2015-02-05 17:26:18 +01:00
gdkmirscreen.c Rework window construction - only recreate surface when necessary 2016-08-10 13:36:38 -04:00
gdkmirwindow.c Gdk: add an experimental backend for mir 2014-10-22 11:17:15 -05:00
gdkmirwindowimpl.c Only apply type hint if it would map to a different mir surface type 2016-08-10 13:41:27 -04:00
Makefile.am Opt in to structured logging 2016-07-22 23:13:20 -04:00