diff options
author | Stein <bakkeby@gmail.com> | 2022-08-09 10:38:08 +0200 |
---|---|---|
committer | Hiltjo Posthuma <hiltjo@codemadness.org> | 2022-08-10 15:31:21 +0200 |
commit | a859676ead17017bbe81b4989b2f2e0b00a0b4ba (patch) | |
tree | 6f3dda2ac548478b739c648e36e2a7a60dde660f /dwm.c%2525253fid%2525253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e%25253fid%25253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e%253fid%253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e&id2%253da859676ead17017bbe81b4989b2f2e0b00a0b4ba%3fid%3d6d6e0ea56f6784dd35173eff2d17c259b1588d0e?id=a859676ead17017bbe81b4989b2f2e0b00a0b4ba | |
parent | e0dee911455cee739a5b05a994828f4a37a2764d (diff) |
Simplify client y-offset correction
The reasoning behind the original line may be lost to time as
it does not make much sense checking the position on the x-axis
to determine how to position the client on the y-axis.
In the context of multi-monitor setups the monitor y position
(m->my) may be greater than 0 (say 500), in which case the window
could be placed out of view if:
- the window attributes have a 0 value for the y position and
- we end up using the y position of bh (e.g. 22)
If the aim is to avoid a new floating client covering the bar then
restricting y position to be at least that of the window area
(m->wy) should cover the two cases of using a top bar and using a
bottom bar.
Diffstat (limited to 'dwm.c%2525253fid%2525253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e%25253fid%25253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e%253fid%253d6d6e0ea56f6784dd35173eff2d17c259b1588d0e&id2%253da859676ead17017bbe81b4989b2f2e0b00a0b4ba%3fid%3d6d6e0ea56f6784dd35173eff2d17c259b1588d0e?id=a859676ead17017bbe81b4989b2f2e0b00a0b4ba')
0 files changed, 0 insertions, 0 deletions