aboutsummaryrefslogtreecommitdiff
path: root/dwl.c
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | Merge pull request #53 from Stivvo/fullscreenDevin J. Pohly2020-12-241-20/+105
|\ \ \ \ \ | | | | | | | | | | | | Fullscreen support
| * | | | | Change fullscreen policiesStivvo2020-12-241-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.
| * | | | | quitallfullscreen() even when enabling fullscreenStivvo2020-12-241-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
| * | | | | Remove goto render (easier merge)Stivvo2020-12-241-19/+18
| | | | | |
| * | | | | Readme: achieve fullscreen + allow borderpx = 0Stivvo2020-10-241-2/+2
| | | | | |
| * | | | | Quit fullscreen on new x11 windowStivvo2020-10-141-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After the removal of quitfullscreen() dwl wouldn't compile widh xwayland enabled because createnotifyx11 was still using the old function
| * | | | | Delete quitfullscreen()Stivvo2020-10-141-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
| * | | | | Keep windows fullscreen after redrawStivvo2020-10-081-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
| * | | | | Set fullscreen simplerStivvo2020-10-081-4/+4
| | | | | |
| * | | | | use m->m (fullscreen on top of layers)Stivvo2020-09-161-1/+1
| | | | | |
| * | | | | fix typoGuido Cella2020-09-101-4/+4
| | | | | |
| * | | | | Allow borderpx = 0Stivvo2020-09-061-2/+2
| | | | | |
| * | | | | Toggle fullscreen on all clientsStivvo2020-09-051-3/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mod+e allows to toggle fullscreen any client, even those who don't support it themselves
| * | | | | Handle new windowsStivvo2020-09-051-2/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows lose fullscreen state when a new window is created in the same tag
| * | | | | isfullscreen intStivvo2020-09-051-4/+5
| | | | | |
| * | | | | Same fscreen func for xdg and xwaylandStivvo2020-09-051-32/+14
| | | | | |
| * | | | | Fullscreen xwaylandStivvo2020-09-051-1/+31
| | | | | |
| * | | | | Unlink fullscreenStivvo2020-09-051-0/+1
| | | | | |
| * | | | | Restore windows after fullscreenStivvo2020-09-041-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
| * | | | | No borders on fullscreen windowsStivvo2020-09-041-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | Some code has been borrowed from the smartBorders patch
| * | | | | Toggle fullscreenStivvo2020-09-041-1/+1
| | | | | |
| * | | | | Basic fullscreenStivvo2020-09-041-0/+11
| |/ / / /
* | | | | fix crash on non-libinput pointers (e.g. X11 backend)Devin J. Pohly2020-12-241-5/+7
| | | | |
* | | | | Merge pull request #49 from guidocella/layer-shellDevin J. Pohly2020-12-241-9/+447
|\ \ \ \ \ | | |_|_|/ | |/| | | Layer shell
| * | | | extract function and comment itGuido Cella2020-09-111-11/+18
| | | | |
| * | | | remove bracesGuido Cella2020-09-111-2/+1
| | | | |
| * | | | fix multi monitors even moreGuido Cella2020-09-111-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).
| * | | | simplifyGuido Cella2020-09-101-1/+1
| | | | |
| * | | | fix multi monitors furtherGuido Cella2020-09-091-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Fix layer surfaces without an exculsive area by using the right x and y for the current monitor (by Stivvo).
| * | | | remove unneeded lineGuido Cella2020-09-081-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.
| * | | | try to fix againGuido Cella2020-09-081-4/+1
| | | | | | | | | | | | | | | | | | | | Calculate x and y of usable_area, not just width and heigth.
| * | | | fix multi monitorsGuido Cella2020-09-081-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.
| * | | | remove variableGuido Cella2020-09-061-4/+3
| | | | |
| * | | | use size_t for lengthsGuido Cella2020-09-051-4/+4
| | | | |
| * | | | rename variable and merge 2 linesGuido Cella2020-09-051-3/+2
| | | | |
| * | | | simplifyGuido Cella2020-09-051-10/+4
| | | | |
| * | | | use unsigned int for loop indexesGuido Cella2020-09-041-3/+3
| | | | |
| * | | | Don't let overlays lose focusGuido Cella2020-09-041-2/+20
| | | | | | | | | | | | | | | | | | | | | | | | | if you open a new window while an overlay is mapped, the overlay should stay focused
| * | | | fix restoring pointer focusGuido Cella2020-09-041-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | I don't know why I thought it was working before. Maybe I should go do something else.
| * | | | improve code styleGuido Cella2020-09-041-4/+4
| | | | |
| * | | | remove commentGuido Cella2020-09-041-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)
| * | | | remove mysterious codeGuido Cella2020-09-041-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Why would a surface that's not keyboard interactive get focused? Let's remove this for now and see if issues arise.
| * | | | focus the previous client in the similar code tooGuido Cella2020-09-041-2/+1
| | | | |
| * | | | refocus old clientGuido Cella2020-09-041-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.
| * | | | fix alhpabetical orderGuido Cella2020-09-041-8/+8
| | | | |
| * | | | simplify focus leave conditionGuido Cella2020-09-041-7/+2
| | | | |
| * | | | reuse motionnotify()Guido Cella2020-09-041-10/+8
| | | | |
| * | | | enable pointer on layer surfacesGuido Cella2020-09-041-5/+49
| | | | |
| * | | | more TODOsGuido Cella2020-09-031-2/+3
| | | | |
| * | | | fix focus leave conditionGuido Cella2020-09-031-3/+4
| | | | | | | | | | | | | | | | | | | | needs refactoring and testing