summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-10-25Handle monitor enableStivvo
2020-10-25Move clients away from a disabled monitorStivvo
When a monitor is disabled with wlr_randr, all clients on that monitor aren't lost but they are moved to the leftmost monitor with the same method that handles monitor hot unplug
2020-10-25Merge branch 'handleUnplug' into output-managementStivvo
2020-10-24closemon()Stivvo
Separate oputput movement from cleanupmon
2020-10-24Merge branch 'handleUnplug' into output-managementStivvo
2020-10-24Readme: achieve fullscreen + allow borderpx = 0Stivvo
2020-10-18fix compile error mixed declarationStivvo
2020-10-18Merge pull request #2 from guidocella/handleUnplugStivvo
Move sgeom assignment
2020-10-17Move sgeom assignmentGuido Cella
There is no need to repeat this. This needs to be reculalculated in my output-management implementation too, and since I'm already calling updatemons, this patch avoids having to repeat the assignment again.
2020-10-17Implement the output management protocolGuido Cella
It allows clients such as wlr-randr to configure the display.
2020-10-17Added support for natural scrollingwill
2020-10-17Added basic tap-to-click for touchpad userswill
2020-10-14Quit fullscreen on new x11 windowStivvo
After the removal of quitfullscreen() dwl wouldn't compile widh xwayland enabled because createnotifyx11 was still using the old function
2020-10-14Delete quitfullscreen()Stivvo
quitfullscreen() was replicating the functionalities of setfullscreen(c, 0) Reusing setfullscreen() in quitfullscreen() leads to a 3 line function, which is useless since quitfullscreen() is used once anyway
2020-10-08Keep windows fullscreen after redrawStivvo
This fixes the bug that happens when changing workspace (or any time arrange() is called) where there are fullscreen windows, which are still fullscreen but leave the space for layer surfaces like waybar (which should be hidden when going fullscreen) Also as soon one fullscreen window is found hte function returns to improve efficiency
2020-10-08Set fullscreen simplerStivvo
2020-09-16use m->m (fullscreen on top of layers)Stivvo
2020-09-16Merge pull request #1 from guidocella/fullscreenStivvo
fix typo
2020-09-15Keep client tags on unplugStivvo
When unplugging a monitor, each client is moved to the same tag number as before on the new monitor
2020-09-15Handle monitor unplugStivvo
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-14remove log flags from readmeOyren
The following commit has removed the logs but they are still in the readme. https://github.com/djpohly/dwl/commit/3b1992ca91b9a468019165c985263f5b1cc78c2c
2020-09-12Restore floating win position after mon addStivvo
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 Cella
2020-09-11remove bracesGuido Cella
2020-09-11fix multi monitors even moreGuido Cella
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 Cella
2020-09-10simplifyGuido Cella
2020-09-09fix multi monitors furtherGuido Cella
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 itBonicgamer
2020-09-08remove unneeded lineGuido Cella
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 Cella
Calculate x and y of usable_area, not just width and heigth.
2020-09-08fix multi monitorsGuido Cella
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 Cella
2020-09-06Allow borderpx = 0Stivvo
2020-09-05use size_t for lengthsGuido Cella
2020-09-05rename variable and merge 2 linesGuido Cella
2020-09-05Toggle fullscreen on all clientsStivvo
mod+e allows to toggle fullscreen any client, even those who don't support it themselves
2020-09-05Handle new windowsStivvo
Windows lose fullscreen state when a new window is created in the same tag
2020-09-05isfullscreen intStivvo
2020-09-05Same fscreen func for xdg and xwaylandStivvo
2020-09-05Fullscreen xwaylandStivvo
2020-09-05Unlink fullscreenStivvo
2020-09-05simplifyGuido Cella
2020-09-04use unsigned int for loop indexesGuido Cella
2020-09-04Don't let overlays lose focusGuido Cella
if you open a new window while an overlay is mapped, the overlay should stay focused
2020-09-04fix restoring pointer focusGuido Cella
I don't know why I thought it was working before. Maybe I should go do something else.
2020-09-04improve code styleGuido Cella
2020-09-04remove commentGuido Cella
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 Cella
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 Cella
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-27 06:30:13 +0000