summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarco Trevisan (TreviƱo) <mail@3v1n0.net>2021-03-12 20:12:30 +0100
committerMarge Bot <marge-bot@gnome.org>2021-03-13 21:36:25 +0000
commiteed368ee91c9444d52b3f9a7f8f54abb7703a505 (patch)
tree3419b40a78120159dc3f2e754abe1be92415d170
parenta78a3258e2b3c147f157b5c2098669bc366423e2 (diff)
downloadmutter-eed368ee91c9444d52b3f9a7f8f54abb7703a505.tar.gz
clutter: Always make the seat handle the events first
Some events such as the proximity one requires a device to be set before we process them, so ensure we process the event details after we've added the device to the seat. This may lead to handle a device-removed signal before the clutter event but it's anyways not different from what we did before commit 012c0a18 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1779>
-rw-r--r--clutter/clutter/clutter-main.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/clutter/clutter/clutter-main.c b/clutter/clutter/clutter-main.c
index 2efe8e973..d79b690a3 100644
--- a/clutter/clutter/clutter-main.c
+++ b/clutter/clutter/clutter-main.c
@@ -1909,8 +1909,8 @@ _clutter_process_event (ClutterEvent *event)
*/
context->current_event = g_slist_prepend (context->current_event, event);
- _clutter_process_event_details (stage, context, event);
clutter_seat_handle_event_post (seat, event);
+ _clutter_process_event_details (stage, context, event);
context->current_event = g_slist_delete_link (context->current_event, context->current_event);
}