Don't call map_win() in add_win()
Only case where you want to map window in add_win() is during compton startup, when compton is registering existing windows. Otherwise, add_win() is always called for newly created windows, so there will always be a MapNotify coming up for that window. If we map newly created windows in add_win(), we will try to map it a second time when the MapNotify arrives. So, just don't call map_win() from add_win(). For compton startup, we explicitly call map_win() after calling add_win() in session_init. Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
This commit is contained in:
@ -359,6 +359,9 @@ void add_win(session_t *ps, xcb_window_t id, xcb_window_t prev);
|
||||
/// Unmap or destroy a window
|
||||
void unmap_win(session_t *ps, win **, bool destroy);
|
||||
|
||||
void map_win(session_t *ps, win *w);
|
||||
void map_win_by_id(session_t *ps, xcb_window_t id);
|
||||
|
||||
/**
|
||||
* Execute fade callback of a window if fading finished.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user