From 72c433ef023e076d3f4e4e49bd3a62b1befa619f Mon Sep 17 00:00:00 2001 From: Carlos Garnacho Date: Tue, 1 Aug 2023 01:58:39 +0300 Subject: [PATCH] compositor: Stop forwarding MapNotify events back through the backend Nowadays, all our MapNotify event handling happens already prior to the MetaCompositorX11 handling of XEvents. It does not make sense to channel these events again through the backend, at best all it could lead to is double handling of the same events. Part-of: --- src/compositor/meta-compositor-x11.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/src/compositor/meta-compositor-x11.c b/src/compositor/meta-compositor-x11.c index 74f77b48f..fae69d4cd 100644 --- a/src/compositor/meta-compositor-x11.c +++ b/src/compositor/meta-compositor-x11.c @@ -75,7 +75,6 @@ meta_compositor_x11_process_xevent (MetaCompositorX11 *compositor_x11, { MetaCompositor *compositor = META_COMPOSITOR (compositor_x11); MetaDisplay *display = meta_compositor_get_display (compositor); - MetaBackend *backend = meta_compositor_get_backend (compositor); MetaX11Display *x11_display = display->x11_display; int damage_event_base; @@ -100,13 +99,6 @@ meta_compositor_x11_process_xevent (MetaCompositorX11 *compositor_x11, if (compositor_x11->have_x11_sync_object) meta_sync_ring_handle_event (xevent); - - /* - * Clutter needs to know about MapNotify events otherwise it will think the - * stage is invisible - */ - if (xevent->type == MapNotify) - meta_x11_handle_event (backend, xevent); } static void