| commit | 3cbb59b0dcadc9e2894aad6b252e81a1c0c6ed9e | |
| author | Uli Schlachter <psychon@znc.in> | |
| Wed, 16 May 2012 21:03:32 +0000 (16 23:03 +0200) | ||
| committer | Uli Schlachter <psychon@znc.in> | |
| Wed, 16 May 2012 21:03:32 +0000 (16 23:03 +0200) | ||
| tree | d3a8d503d4cb32a8013bad12ee249667d0ab769b | treesnapshot (tar.gz zip) |
| parent | 4170c77a08a3257858b004ea13b469f8eef0832b | commitdiff |
FS#996: awful.ewmh: Connect to property::border_width signal
For example, I have some lua code which sets the border width based on the
number of visible clients. When just a single client is visible, the border
width is 0, else it's what the theme says.
Previously, this caused visible "glitches" for fullscreen'd and maximized
clients. This patch fixes that and updates the client's geometry and
border width appropriately.
This has a slight chance of going into an endless loop if someone sets a
fullscreen'd clients border width from its property::border_width signal.
Just don't do that!
Thanks to Arvydas Sidorenko for finding this issue.
Signed-off-by: Uli Schlachter <psychon@znc.in>
For example, I have some lua code which sets the border width based on the
number of visible clients. When just a single client is visible, the border
width is 0, else it's what the theme says.
Previously, this caused visible "glitches" for fullscreen'd and maximized
clients. This patch fixes that and updates the client's geometry and
border width appropriately.
This has a slight chance of going into an endless loop if someone sets a
fullscreen'd clients border width from its property::border_width signal.
Just don't do that!
Thanks to Arvydas Sidorenko for finding this issue.
Signed-off-by: Uli Schlachter <psychon@znc.in>
| lib/awful/ewmh.lua.in | diffblobblamehistory |