Considering _net_wm_state?

answered 2013-12-09 19:45:34 +0000

Michael
3081 ●13 ●28 ●50 http://i3wm.org/

Report 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... for what i3 makes floating. The most likely candidate for your case seems to be setting the leader window on the dialog window.

edit flag offensive delete link

Comments

What 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 unmanaged

milkypostman ( 2013-12-09 20:00:46 +0000 )edit

add a comment

Considering _net_wm_state?

1 answer

Comments

Question Tools

Stats