2009-02-14 02:33:31 +01:00
|
|
|
/*
|
|
|
|
* vim:ts=8:expandtab
|
|
|
|
*
|
|
|
|
* i3 - an improved dynamic tiling window manager
|
|
|
|
*
|
2010-03-02 12:47:21 +01:00
|
|
|
* © 2009-2010 Michael Stapelberg and contributors
|
2009-02-14 02:33:31 +01:00
|
|
|
*
|
|
|
|
* See file LICENSE for license information.
|
|
|
|
*
|
|
|
|
*/
|
2009-02-13 19:04:45 +01:00
|
|
|
#ifndef _HANDLERS_H
|
|
|
|
#define _HANDLERS_H
|
|
|
|
|
2010-03-02 12:47:21 +01:00
|
|
|
#include <xcb/randr.h>
|
|
|
|
|
2011-03-18 14:36:36 +01:00
|
|
|
extern int randr_base;
|
2010-04-13 20:51:43 +02:00
|
|
|
|
Bugfix: Ignore EnterNotifies generated by UnmapNotifies
Actually, commit 1c5adc6c35cffaedc08c7d1dd1b03a3269d1367c commented out code
without ever fixing it. I think this was responsible for the 'workspace
switching sometimes does not work' bug. My observations:
Had it again today and analyzed a log of it. Looks like after unmapping the
windows on one workspace (in my case: chromium, eclipse, urxvt, focus on
eclipse) we get UnmapNotify events for chromium and eclipse, but then we get an
EnterNotify for the terminal (due to unmapping the other windows and therefore
mapping the terminal under the cursor), only afterwards the UnmapNotify
follows.
So, there are two things wrong with that:
• We handle EnterNotifys for unmapped windows
• Unmapping windows sometimes works in a sequence, sometimes the sequence gets
split. Not sure why (if unmapping can take longer for some windows or if our
syncing is wrong -- but i checked the latter briefly and it looks correct).
Maybe GrabServer helps?
• We don’t ignore EnterNotify events caused by UnmapNotifies. We used to, but
then there was a different problem and we decided to solve the EnterNotify
problem in another way, which actually never happened (commit
1c5adc6c35cffaedc08c7d1dd1b03a3269d1367c).
2011-04-19 21:50:56 +02:00
|
|
|
void add_ignore_event(const int sequence, const int response_type);
|
2010-04-13 20:51:43 +02:00
|
|
|
|
2011-03-18 14:36:36 +01:00
|
|
|
/**
|
|
|
|
* Takes an xcb_generic_event_t and calls the appropriate handler, based on the
|
|
|
|
* event type.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
void handle_event(int type, xcb_generic_event_t *event);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Sets the appropriate atoms for the property handlers after the atoms were
|
|
|
|
* received from X11
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
void property_handlers_init();
|
|
|
|
|
2010-04-13 19:33:40 +02:00
|
|
|
#if 0
|
2009-04-07 19:02:07 +02:00
|
|
|
/**
|
2009-06-29 21:54:51 +02:00
|
|
|
* Configuration notifies are only handled because we need to set up ignore
|
|
|
|
* for the following enter notify events
|
2009-04-07 19:02:07 +02:00
|
|
|
*
|
|
|
|
*/
|
2009-02-28 22:11:48 +01:00
|
|
|
int handle_configure_event(void *prophs, xcb_connection_t *conn, xcb_configure_notify_event_t *event);
|
2011-01-05 00:16:10 +01:00
|
|
|
#endif
|
2009-04-07 19:02:07 +02:00
|
|
|
|
2010-04-17 13:54:45 +02:00
|
|
|
#if 0
|
2009-04-07 19:02:07 +02:00
|
|
|
/**
|
|
|
|
* Handles _NET_WM_WINDOW_TYPE changes
|
|
|
|
*
|
|
|
|
*/
|
2009-06-29 21:54:51 +02:00
|
|
|
int handle_window_type(void *data, xcb_connection_t *conn, uint8_t state,
|
|
|
|
xcb_window_t window, xcb_atom_t atom,
|
|
|
|
xcb_get_property_reply_t *property);
|
2010-10-11 21:32:04 +02:00
|
|
|
#endif
|
2009-04-07 19:02:07 +02:00
|
|
|
|
2009-02-13 19:04:45 +01:00
|
|
|
#endif
|