isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-22 08:00:42 -05:00
Code Issues Packages Projects Releases Wiki Activity

compositor: Stop forwarding MapNotify events back through the backend

Browse Source 
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: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3153>
This commit is contained in:
Carlos Garnacho 2023-08-01 01:58:39 +03:00
parent b2dc5b72a1
commit 72c433ef02
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/compositor/meta-compositor-x11.c
View File

@ -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