Closed avaly closed 7 years ago
Sorry for not responding earlier. Bit of a busy day. I'll have to test this a bit, but I'll try to get to it tomorrow or the following day.
If I can make time to work on QuickTile, this problem will get an even better solution, since I want to rework the tiling so that it actually calculates a grid and then just snaps windows into it. (Among other things, that'll provide for functionality like #10, which would allow a single keypress to resize all windows sharing a row/column with the current one.)
Sorry again for putting this off. To be perfectly honest, I just caught myself procrastinating trying to reverse-engineer the COLUMN_COUNT
value which exhibits the problem so I could test the effects.
Mind telling me?
I used COLUMN_COUNT = 10
for the example above.
Hmm. COLUMN_COUNT = 10
and no other change produces broken results on my system with either version of the codebase. I think this might just be untestable on my 1280x1024
monitors.
That said, I don't see any significant regressions with the default COLUMN_COUNT = 3
.
It does change a known bug (there's a 1px
gap that moves from between columns 2 and 3 to between columns 1 and 2) but that's no reason to keep from merging it.
...and I really need to stop putting off setting up the types of automated regression tests which require a mock X server on Travis CI. This could've been done in 2 minutes if I'd automated that.
Without this for certain
COLUMN_COUNT
values, I see the followingpositions
: