aboutsummaryrefslogtreecommitdiffstats
path: root/dwl.c
AgeCommit message (Collapse)AuthorLines
2020-12-24Merge pull request #54 from Bonicgamer/swayscaleboxDevin J. Pohly-4/+5
Sway scale_box (rounding)
2020-12-24Merge pull request #53 from Stivvo/fullscreenDevin J. Pohly-20/+105
Fullscreen support
2020-12-24fix crash on non-libinput pointers (e.g. X11 backend)Devin J. Pohly-5/+7
2020-12-24Merge pull request #49 from guidocella/layer-shellDevin J. Pohly-9/+447
Layer shell
2020-12-24Merge pull request #62 from Java-boi/masterDevin J. Pohly-0/+11
Added basic tap-to-click for touchpad users
2020-12-24Change fullscreen policiesStivvo-25/+30
When a new client is spawned, fullscreen isn't disabled for all clients in that monitor any more. Instead, all fullscreen clients are kept fullscreen, while other clients spawn in the background. When fullscreen is disabled, all clients are rearranged. This is made to make dwl more flexible allowing multiple fullscreen clients at the same time, have floating clients on top of a fullscreen one and let stuff happen without quitting fullscreen, like many other WMs and DEs.
2020-12-24quitallfullscreen() even when enabling fullscreenStivvo-7/+14
Disable fullscreen on all visible clients in that monitor also before enabling it on another client. quitallfullscreen() is reintroduced becouse is now more useful set c->isfullscreen later to avoid making quitallfullscreen() disable fullscreen on the current client
2020-12-24Remove goto render (easier merge)Stivvo-19/+18
2020-11-23fix undeclared WLR_KEY_PRESSEDRichard Ipsum-1/+1
2020-10-24Readme: achieve fullscreen + allow borderpx = 0Stivvo-2/+2
2020-10-17Added support for natural scrollingwill-0/+5
2020-10-17Added basic tap-to-click for touchpad userswill-0/+6
2020-10-14Quit fullscreen on new x11 windowStivvo-3/+4
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-20/+4
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-0/+8
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-4/+4
2020-09-16use m->m (fullscreen on top of layers)Stivvo-1/+1
2020-09-11extract function and comment itGuido Cella-11/+18
2020-09-11remove bracesGuido Cella-2/+1
2020-09-11fix multi monitors even moreGuido Cella-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 Cella-4/+4
2020-09-10simplifyGuido Cella-1/+1
2020-09-09fix multi monitors furtherGuido Cella-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 itBonicgamer-4/+5
2020-09-08remove unneeded lineGuido Cella-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 Cella-4/+1
Calculate x and y of usable_area, not just width and heigth.
2020-09-08fix multi monitorsGuido Cella-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 Cella-4/+3
2020-09-06Allow borderpx = 0Stivvo-2/+2
2020-09-05use size_t for lengthsGuido Cella-4/+4
2020-09-05rename variable and merge 2 linesGuido Cella-3/+2
2020-09-05Toggle fullscreen on all clientsStivvo-3/+18
mod+e allows to toggle fullscreen any client, even those who don't support it themselves
2020-09-05Handle new windowsStivvo-2/+22
Windows lose fullscreen state when a new window is created in the same tag
2020-09-05isfullscreen intStivvo-4/+5
2020-09-05Same fscreen func for xdg and xwaylandStivvo-32/+14
2020-09-05Fullscreen xwaylandStivvo-1/+31
2020-09-05Unlink fullscreenStivvo-0/+1
2020-09-05simplifyGuido Cella-10/+4
2020-09-04use unsigned int for loop indexesGuido Cella-3/+3
2020-09-04Don't let overlays lose focusGuido Cella-2/+20
if you open a new window while an overlay is mapped, the overlay should stay focused
2020-09-04fix restoring pointer focusGuido Cella-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 Cella-4/+4
2020-09-04remove commentGuido Cella-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 Cella-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 Cella-2/+1
2020-09-04refocus old clientGuido Cella-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 fullscreenStivvo-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 windowsStivvo-1/+8
Some code has been borrowed from the smartBorders patch
2020-09-04fix alhpabetical orderGuido Cella-8/+8
2020-09-04simplify focus leave conditionGuido Cella-7/+2
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-29 10:07:58 +0000