i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Mon, 09 Dec 2013 20:00:46 +0000Considering _net_wm_state?https://faq.i3wm.org/question/3025/considering-_net_wm_state/Is there a way to get i3 to recognize things about the `_NET_WM_STATE`? I have a window I want to be floating but there is no way to distinguish it except that it doesn't have a `WM_WINDOW_ROLE` (`for_window` seems to skip `window_role` when `WM_WINDOW_ROLE` is missing) and it sets, _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STICKY, _NET_WM_STATE_SKIP_TASKBAR Basically, I'd like to recognize any window that has `_NET_WM_STATE_ABOVE` as a floating window.Mon, 09 Dec 2013 19:18:27 +0000https://faq.i3wm.org/question/3025/considering-_net_wm_state/Answer by Michael for Is there a way to get i3 to recognize things about the <code>_NET_WM_STATE</code>? I have a window I want to be floating but there is no way to distinguish it except that it doesn't have a <code>WM_WINDOW_ROLE</code> (<code>for_window</code> seems to skip <code>window_role</code> when <code>WM_WINDOW_ROLE</code> is missing) and it sets, <pre><code>_NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STICKY, _NET_WM_STATE_SKIP_TASKBAR </code></pre> Basically, I'd like to recognize any window that has <code>_NET_WM_STATE_ABOVE</code> as a floating window. https://faq.i3wm.org/question/3025/considering-_net_wm_state/?answer=3026#post-id-3026Report a bug upstream for the application this is about. `_NET_WM_STATE_ABOVE` is certainly not the right criterion to make something floating. Quote from the standard: _NET_WM_STATE_ABOVE indicates that the window should be on top of most windows (see the section called “Stacking order” for details). _NET_WM_STATE_BELOW indicates that the window should be below most windows (see the section called “Stacking order” for details). _NET_WM_STATE_ABOVE and _NET_WM_STATE_BELOW are mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs (the Urgency hint should be used in that case, see the section called “Urgency”).' See http://code.stapelberg.de/git/i3/tree/src/manage.c?h=next#n375 for what i3 makes floating. The most likely candidate for your case seems to be setting the leader window on the dialog window.Mon, 09 Dec 2013 19:45:34 +0000https://faq.i3wm.org/question/3025/considering-_net_wm_state/?answer=3026#post-id-3026Comment by milkypostman for Report a bug upstream for the application this is about. <code>_NET_WM_STATE_ABOVE</code> is certainly not the right criterion to make something floating. Quote from the standard: <pre><code>_NET_WM_STATE_ABOVE indicates that the window should be on top of most windows (see the section called “Stacking order” for details). _NET_WM_STATE_BELOW indicates that the window should be below most windows (see the section called “Stacking order” for details). _NET_WM_STATE_ABOVE and _NET_WM_STATE_BELOW are mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs (the Urgency hint should be used in that case, see the section called “Urgency”).' </code></pre> See <a href="http://code.stapelberg.de/git/i3/tree/src/manage.c?h=next#n375">http://code.stapelberg.de/git/i3/tree...</a> for what i3 makes floating. The most likely candidate for your case seems to be setting the leader window on the dialog window. https://faq.i3wm.org/question/3025/considering-_net_wm_state/?comment=3028#comment-3028What about `_NET_WM_STATE_STICKY` which states that the window should keep the window's position fixed? Also `_NET_WM_STATE_SKIP_TASKBAR`. With both of those enabled, it seems like the application doesn't want to be controlled and in most other WMs, like gnome, this causes the window to be unmanagedMon, 09 Dec 2013 20:00:46 +0000https://faq.i3wm.org/question/3025/considering-_net_wm_state/?comment=3028#comment-3028