aboutsummaryrefslogtreecommitdiffhomepage
path: root/dwl.c
AgeCommit message (Collapse)AuthorFilesLines
2020-09-15Keep client tags on unplugStivvo1-1/+1
When unplugging a monitor, each client is moved to the same tag number as before on the new monitor
2020-09-15Handle monitor unplugStivvo1-16/+25
Floating widndows with "x < removed monitor's width" aren't resized (they used to disappear in negative coordinates). Actually delete monitors when they are unplugged, recalculate sgeom and give a new monitor to clients that were on the removed one with setmon() arrangefloat() funcion has been exploded to save iterations in cleanupmon(). Also if a monitor that supports auto suspension is turned off, dwl will count it as unplugged (it will become unreachable and all clients will be moved to the leftmost monitor). However, if at least one monitor isn't plugged in, dwl will still crash the same as before. Unlike sway, when the output configuration is changed and restored, (unplug + plug the same monitor for example) previous application positions aren't kept. This is due to the fact that on sway every workspace is unique among all monitors.
2020-09-12Restore floating win position after mon addStivvo1-0/+18
Compensate the coordinate changes when adding a new monitor. Every test so far confirms that monitors are always added to the left, on top of the list, so every floating window's x coordinate has to be incremented by the width of the new monitor.
2020-09-11extract function and comment itGuido Cella1-11/+18
2020-09-11remove bracesGuido Cella1-2/+1
2020-09-11fix multi monitors even moreGuido Cella1-6/+15
When a monitor is created or removed, the geometries of the old ones must be updated. This is also more efficient than before since we calculate the monitor geometries only when creating and destroying monitors. arrangelayers() is needed to recalculate m->w. arrange() is so clients don't move to the left monitor when plugging or unplugging monitors (clients keep the same coordinates but the field below them changes).
2020-09-10fix typoGuido Cella1-4/+4
2020-09-10simplifyGuido Cella1-1/+1
2020-09-09fix multi monitors furtherGuido Cella1-3/+1
Fix layer surfaces without an exculsive area by using the right x and y for the current monitor (by Stivvo).
2020-09-08Made scalebox the way sway does itBonicgamer1-4/+5
2020-09-08remove unneeded lineGuido Cella1-1/+0
The bug was caused by usable_area's x and y not being set in arrangelayers. For example if on a 2nd HD monitor, x should be 1920 while the first one ends at 1919. So I don't see why m->m should be recalculated after creating the monitor.
2020-09-08try to fix againGuido Cella1-4/+1
Calculate x and y of usable_area, not just width and heigth.
2020-09-08fix multi monitorsGuido Cella1-1/+5
If you don't recalculate the monitor's geometry before arranging, clients get arranged in the first monitor. I don't understand why this fixes the bug since tile() uses m->w rather than m->m, nor why it needs to be recalculated after creating the monitor but sway does it too. Although not necessary to fix the bug I also made arrangelayer() do like sway again and recalculate usable_area instead of reusing m->m, since m->m seems to be incorrect until it gets recalculated shortly after in arrange(), so I suspect that leaving usable_area = m->m will cause issues under certain circumstances. Someone with a multi-monitor setup or better knowledge of Wayland may be able to figure out the cause of the bug. For now, this makes layer shell work.
2020-09-06remove variableGuido Cella1-4/+3
2020-09-06Allow borderpx = 0Stivvo1-2/+2
2020-09-05use size_t for lengthsGuido Cella1-4/+4
2020-09-05rename variable and merge 2 linesGuido Cella1-3/+2
2020-09-05Toggle fullscreen on all clientsStivvo1-3/+18
mod+e allows to toggle fullscreen any client, even those who don't support it themselves
2020-09-05Handle new windowsStivvo1-2/+22
Windows lose fullscreen state when a new window is created in the same tag
2020-09-05isfullscreen intStivvo1-4/+5
2020-09-05Same fscreen func for xdg and xwaylandStivvo1-32/+14
2020-09-05Fullscreen xwaylandStivvo1-1/+31
2020-09-05Unlink fullscreenStivvo1-0/+1
2020-09-05simplifyGuido Cella1-10/+4
2020-09-04use unsigned int for loop indexesGuido Cella1-3/+3
2020-09-04Don't let overlays lose focusGuido Cella1-2/+20
if you open a new window while an overlay is mapped, the overlay should stay focused
2020-09-04fix restoring pointer focusGuido Cella1-1/+6
I don't know why I thought it was working before. Maybe I should go do something else.
2020-09-04improve code styleGuido Cella1-4/+4
2020-09-04remove commentGuido Cella1-1/+1
I don't know why it wasn't working before but now it does ¯\(ツ)/¯ (it wasn't caused by the just removed code either)
2020-09-04remove mysterious codeGuido Cella1-7/+0
Why would a surface that's not keyboard interactive get focused? Let's remove this for now and see if issues arise.
2020-09-04focus the previous client in the similar code tooGuido Cella1-2/+1
2020-09-04refocus old clientGuido Cella1-3/+1
When a layer surface is destroyed focus should be returned to the last client. Luckily if there are multiple overlays the previous overlay still gets focused.
2020-09-04Restore windows after fullscreenStivvo1-0/+14
Store position and size of windows before going fullscreen. This is more efficient than arrange() and also works with floating windows All the clients keep their original position because arrange() isn't used after quitting fullscreen
2020-09-04No borders on fullscreen windowsStivvo1-1/+8
Some code has been borrowed from the smartBorders patch
2020-09-04fix alhpabetical orderGuido Cella1-8/+8
2020-09-04simplify focus leave conditionGuido Cella1-7/+2
2020-09-04reuse motionnotify()Guido Cella1-10/+8
2020-09-04Toggle fullscreenStivvo1-1/+1
2020-09-04Basic fullscreenStivvo1-0/+11
2020-09-04enable pointer on layer surfacesGuido Cella1-5/+49
2020-09-03more TODOsGuido Cella1-2/+3
2020-09-03fix focus leave conditionGuido Cella1-3/+4
needs refactoring and testing
2020-09-03send pressed keys to topmost layer surfaceGuido Cella1-2/+3
2020-08-29remove blank lineGuido Cella1-1/+0
2020-08-29don't handle failed callocGuido Cella1-2/+0
be consistent with the rest of the code
2020-08-29order variables more how like they are initializedGuido Cella1-1/+1
2020-08-28Reuse render() and struct timespec *nowGuido Cella1-36/+14
2020-08-27reuse m->mGuido Cella1-4/+1
2020-08-27remove commentGuido Cella1-2/+0
wlr_output_layout_get_box internally calls wlr_output_effective_resolution
2020-08-27set a monitor geometry only when creating itGuido Cella1-3/+4
Lets layers with an exclusive area shrink the usable area
generated by cgit (git 2.46.0) at 2025-12-06 19:09:21 +0000