e1bad41fc8
There are some cases where a client's floating state "silently" changes. For example, a fullscreen client will be considered floating. However, even though c.floating changes its value in this case, we did not emit the property::floating signal. Fix this by explicitly tracking the "implicitly floating" state. When some property that influences this "implicitly floating" state changes, we update it and if a client which was not explicitly assigned a floating state observes a change in this value, property::floating is emitted. This was tested by running a terminal and two xeyes in a tag with a tiling layout where awful.ewmh was patched so that clients do not change their geometry when fullscreening or maximizing. It was observable that after this patch e.g. the titlebar and the tasklist update to show the floating state of the client which became implicitly floating due to being maximized. Fixes: https://github.com/awesomeWM/awesome/issues/1662 Signed-off-by: Uli Schlachter <psychon@znc.in> |
||
|---|---|---|
| .. | ||
| awful | ||
| beautiful | ||
| gears | ||
| menubar | ||
| naughty | ||
| wibox | ||
| beautiful.lua | ||
| naughty.lua | ||