summaryrefslogtreecommitdiff
path: root/dwl.c
AgeCommit message (Collapse)Author
2020-12-19isfullscreen intStivvo
2020-12-19Same fscreen func for xdg and xwaylandStivvo
2020-12-19Fullscreen xwaylandStivvo
2020-12-19Unlink fullscreenStivvo
2020-12-19Restore windows after fullscreenStivvo
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-12-19No borders on fullscreen windowsStivvo
Some code has been borrowed from the smartBorders patch
2020-12-19Toggle fullscreenStivvo
2020-12-19Basic fullscreenStivvo
2020-12-19handle the x11 configure eventGuido Cella
This fixes the window size of old games in Wine.
2020-12-19implement the virtual keyboard protocolGuido Cella
This is used by wtype. Also properly cleanup keyboards. Without wl_list_remove(&kb->link) dwl crashed after using wtype 2-3 times.
2020-12-19Allow toggling the layout before selecting a different oneGuido Cella
2020-12-19Implement the idle protocolGuido Cella
It allows clients such as swayidle and chat applications to monitor user idle time.
2020-12-19deactivate focused client when spawning a new oneGuido Cella
Because maprequest immediately calls wl_list_insert(&fstack, &c->flink), in the following call to setmon(), the selclient() which is passed to focusclient() as the old client is actually the newly mapped client, and the real old one is never deactivated. You can see this by, for example, opening Chromium's devtools, then spawning a terminal. The background of the focused line in the devtools doesn't change from light blue to grey. We can't just remove wl_list_insert(&fstack, &c->flink) from maprequest, because calling wl_list_remove in focusclient() with a client that has not been added to the list causes a segmentation fault. Therefore we fix the focusclient call by not passing it the old client every time, but instead using the wlroots function that gets the focused surface and deactivate that, like in TinyWL. This also avoids getting the selected client and passing it to focusclient() on every call unnecessarily, and will allow removing shouldfocusclients in a future commit by checking if old is a layer surface instead.
2020-12-19implement the wlr-data-transfer protocolGuido Cella
It makes wl-clipboard work properly in neovim, without having to create a transparent surface that steals focus and causes flickering. It's also required for clipman.
2020-12-19fix temporarily disabling a single monitorGuido Cella
The code in this else completely freezes my system when I run the swayidle command to replicate xset dpms force off. No idea if it works on multiple monitors, but for now avoid running when there's 1 monitor. Also remove the comment with the function name in sway.
2020-10-31Don't switch to another disabled monitorsStivvo
Since wlr_output_enable doesn't have any effect before finishing all the procedure, a little hack allows to make use of focusmon(), which must know the latest in about which output is currently disabled Also improve performance in focusmon() and cleaner code in outputmgrapplyortest()
2020-10-31Fix crash with no monitors leftStivvo
When there's no monitors left, prevent the while in cleanupmon() to become an infinite loop Also switch to the left monitors instead of the right
2020-10-31closemon() has now only 1 parameterStivvo
2020-10-31Don't switch to disabled mons after unplugStivvo
2020-10-31Merge branch 'handleUnplug' into output-managementStivvo
2020-10-31Back to closemon() with one parameterStivvo
With the recent changes in output-management, the extra argument in closemon() would be needed only when unplugging the monitor, so it isn't worth it anymore. Also now is more efficient.
2020-10-31Disable mon fasterStivvo
Since focusmon() now never focuses disabled monitors, there's no need to focus the disabled monitor first
2020-10-31Fix crash when disabling focused monStivvo
m->link.next leads to errors if the monitor to disable doesn't have a "next" (right) monitor and is currently focused. dirtmon() does more checks. In some previous commits m->link.next is told to be left monitor, which is wrong Also focusclient() explicitly checks for disabled monitors (this fixes in case of more than one disabled monitor)
2020-10-31Fix crash unplugging focused mon 2Stivvo
Focus the top client on newmon, which we know for sure that it isn't going to be unplugged or disabled and actually set that as the focused monitor to move the focus. This is necessary to prevent crash when disabling monitors with the output-management patch.
2020-10-31Merge branch 'handleUnplug' into output-managementStivvo
2020-10-31Fix crash unplugging a focused monStivvo
Focus newmon, which we know for sure that it isn't be unplugged or disabled
2020-10-31Focus client on a new monitor before closingStivvo
2020-10-30Block access to disabled monitorStivvo
Before this, pressing mod+comma or mod+period (focusmon function) moved the focus to disabed monitors. Now, all disabled monitors are skipped
2020-10-30Move disabled clients to the leftStivvo
To the nearest monitor to the left of the disabled one
2020-10-30Merge branch 'handleUnplug' into output-managementStivvo
2020-10-30Merge branch 'handleUnplug' of http://olidata.stivvo01.com:3000/Stivvo01/dwl ↵Stivvo
into handleUnplug
2020-10-30Closemon(), newmon as parameterStivvo
This allows to fix output-management: move clients to the monitor on the left of the disabled one, instead of the leftmost (which might happen to be the disabled one) Also using wl_list_foreach() and then brake after the first iteration is ugly and inefficient
2020-10-30Actually move clients away from a disabled monStivvo
When using wlr-randr every monitor's configuration is reevaluated, so it must check which monitors are actually being disabled. The only way to correctly do that is to compare the names.
2020-10-30Merge branch 'handleUnplug' into output-managementStivvo
2020-10-30Fix crash when unplugging a focused monitorStivvo
Just focus a "safe" monitor before trying to to anything risky
2020-10-30Cleaner if statementStivvo
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-18fix compile error mixed declarationStivvo
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-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-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).
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-25 18:47:41 +0000