applications/i3
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Don’t ignore sequence in UnmapNotify, there might be multiple windows in one sequence

Browse Source 
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.
This commit is contained in:
Michael Stapelberg 2010-06-02 17:03:26 +02:00
parent a7d2c5942a
commit 1c5adc6c35
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/handlers.c
View File

@ -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); 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 /* we need to ignore EnterNotify events which will be generated because a
* different window is visible now */ * 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); DLOG("UnmapNotify for 0x%08x (received from 0x%08x), serial %d\n", event->window, event->event, event->sequence);
if (ignored) { if (ignored) {