core: Add a copy of GDK_PRIORITY_EVENTS

Quoting Carlos:
The META_PRIORITY_EVENTS ± 1 happening below are in order to set these idles
and timeouts in a priority that is relative to the literal GDK event priority,
making those diverge is a likely way to sneakily break things.
But that's unlikely to happen, and decoupling mutter from GTK further
should make it moot, so perhaps it's alright after all.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2407>
This commit is contained in:
Bilal Elmoussaoui
2022-05-09 11:48:57 +02:00
parent 809eaf6e91
commit abef37f5ee
4 changed files with 16 additions and 2 deletions

View File

@ -126,6 +126,9 @@ test_client = executable('mutter-test-client',
gio_unix_dep,
x11_dep,
xext_dep,
graphene_dep,
json_glib_dep,
gsettings_desktop_schemas_dep,
],
install: have_installed_tests,
install_dir: mutter_installed_tests_libexecdir,

View File

@ -28,6 +28,8 @@
#include <string.h>
#include <X11/extensions/sync.h>
#include "core/events.h"
const char *client_id = "0";
static gboolean wayland;
GHashTable *windows;
@ -156,7 +158,7 @@ ensure_xsource_handler (GdkDisplay *gdkdisplay)
x_source->event_poll_fd.events = G_IO_IN;
g_source_add_poll (source, &x_source->event_poll_fd);
g_source_set_priority (source, GDK_PRIORITY_EVENTS - 1);
g_source_set_priority (source, META_PRIORITY_EVENTS - 1);
g_source_set_can_recurse (source, TRUE);
g_source_attach (source, NULL);