From 1c5adc6c35cffaedc08c7d1dd1b03a3269d1367c Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Wed, 2 Jun 2010 17:03:26 +0200 Subject: [PATCH] =?utf8?q?Don=E2=80=99t=20ignore=20sequence=20in=20UnmapNo?= =?utf8?q?tify,=20there=20might=20be=20multiple=20windows=20in=20one=20seq?= =?utf8?q?uence?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit This would lead to i3 thinking that a new window was already managed if it has the same X-ID as the old window. Instead, we need to fix the EnterNotify problem in a different way. --- src/handlers.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/handlers.c b/src/handlers.c index e351aea0..91872e4b 100644 --- a/src/handlers.c +++ b/src/handlers.c @@ -454,9 +454,11 @@ int handle_unmap_notify_event(void *data, xcb_connection_t *conn, xcb_unmap_noti bool ignored = event_is_ignored(event->sequence); + /* FIXME: we cannot ignore this sequence because more UnmapNotifys with the same sequence + * numbers but different window IDs may follow */ /* we need to ignore EnterNotify events which will be generated because a * different window is visible now */ - add_ignore_event(event->sequence); + //add_ignore_event(event->sequence); DLOG("UnmapNotify for 0x%08x (received from 0x%08x), serial %d\n", event->window, event->event, event->sequence); if (ignored) { -- 2.39.5