Open sw9 opened 7 years ago
@sw9 I could only get awful.tag.incmwfact
to work on certain layouts (awful.layout.layouts
). For example, it works with awful.layout.suit.tile,
and awful.layout.suit.tile.left,
, but it does not work on awful.layout.suit.fair,
. I suppose that would make it unfair. ;)
i would start with trying in the latest AwesomeWM git revision as a lot of things changed from 4.1
@sw9 I could only get
awful.tag.incmwfact
to work on certain layouts (awful.layout.layouts
). For example, it works withawful.layout.suit.tile,
andawful.layout.suit.tile.left,
, but it does not work onawful.layout.suit.fair,
. I suppose that would make it unfair. ;)
You're right. That's about how clients layouts are supposed to work.
The documentation doesn't make it obvious but layouts don't have to implement all features / respect all "rules" (generally speaking "rules" like client size, placement and so on, not awful.rules).
Output of
awesome --version
: awesome v4.1 (Technologic) • Compiled against Lua 5.1.5 (running with Lua 5.1) • D-Bus support: ✔ • execinfo support: ✔ • xcb-randr version: 1.4 • LGI version: 0.9.1How to reproduce the issue:
Actual result: Decreasing the master width factor has no effect after a certain point because tile_group sets width to size = math.max(size_hint, size) without checking size_hints_honor. Also, if you want to increase the master width factor, you have to call awful.tag.incmwfact( 0.05) repeatedly before the width actually changes, since mwfact was decreased even while the actual width of the master window didn't change.
Expected result: min_width should be ignored if size_hints_honor is false. Also, if mwfact should not decrease any further if the master window width fails to decrease.