aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* remove togglefullscreen keybindingGuido Cella2020-12-192-9/+0
| | | | | | | | | | | | Distribute it as a patch like in dwm since graphical applications usually provide their own keybinding; I guess it's only for terminals. Note that even though these commits don't let you open multiple windows in fullscreen and cycle between them like in dwm, with just fullscreennotify spawning new windows or changing tag would still exit fullscreen automatically, but you would have to toggle fullscreen twice when switching back to the fullscreen window to enter fullscreen again, so this is better since it avoids that.
* Readme: achieve fullscreen + allow borderpx = 0Stivvo2020-12-192-3/+2
|
* Quit fullscreen on new x11 windowStivvo2020-12-191-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-12-191-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-12-191-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-12-191-4/+4
|
* use m->m (fullscreen on top of layers)Stivvo2020-12-191-1/+1
|
* fix typoGuido Cella2020-12-191-4/+4
|
* Allow borderpx = 0Stivvo2020-12-191-2/+2
|
* Toggle fullscreen on all clientsStivvo2020-12-192-3/+19
| | | | | mod+e allows to toggle fullscreen any client, even those who don't support it themselves
* Handle new windowsStivvo2020-12-191-2/+22
| | | | | Windows lose fullscreen state when a new window is created in the same tag
* isfullscreen intStivvo2020-12-191-4/+5
|
* Same fscreen func for xdg and xwaylandStivvo2020-12-191-32/+14
|
* Fullscreen xwaylandStivvo2020-12-191-1/+31
|
* Unlink fullscreenStivvo2020-12-191-0/+1
|
* Restore windows after fullscreenStivvo2020-12-191-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-12-191-1/+8
| | | | Some code has been borrowed from the smartBorders patch
* Toggle fullscreenStivvo2020-12-191-1/+1
|
* Basic fullscreenStivvo2020-12-191-0/+11
|
* handle the x11 configure eventGuido Cella2020-12-191-0/+13
| | | | This fixes the window size of old games in Wine.
* implement the virtual keyboard protocolGuido Cella2020-12-191-0/+18
| | | | | | | This is used by wtype. Also properly cleanup keyboards. Without wl_list_remove(&kb->link) dwl crashed after using wtype 2-3 times.
* Allow toggling the layout before selecting a different oneGuido Cella2020-12-191-1/+2
|
* Implement the idle protocolGuido Cella2020-12-193-2/+73
| | | | | It allows clients such as swayidle and chat applications to monitor user idle time.
* deactivate focused client when spawning a new oneGuido Cella2020-12-191-26/+24
| | | | | | | | | | | | | | | | | | | | 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.
* implement the wlr-data-transfer protocolGuido Cella2020-12-191-0/+2
| | | | | | 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.
* fix temporarily disabling a single monitorGuido Cella2020-12-191-2/+1
| | | | | | | | 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.
* Don't switch to another disabled monitorsStivvo2020-10-311-15/+15
| | | | | | | | | 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()
* Fix crash with no monitors leftStivvo2020-10-311-4/+3
| | | | | | | 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
* closemon() has now only 1 parameterStivvo2020-10-311-1/+1
|
* Don't switch to disabled mons after unplugStivvo2020-10-311-1/+3
|
* Merge branch 'handleUnplug' into output-managementStivvo2020-10-311-8/+10
|\
| * Back to closemon() with one parameterStivvo2020-10-311-8/+10
| | | | | | | | | | | | 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.
* | Disable mon fasterStivvo2020-10-311-7/+3
| | | | | | | | | | Since focusmon() now never focuses disabled monitors, there's no need to focus the disabled monitor first
* | Fix crash when disabling focused monStivvo2020-10-311-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Merge branch 'handleUnplug' into output-managementStivvo2020-10-310-0/+0
|\|
| * Fix crash unplugging focused mon 2Stivvo2020-10-311-1/+2
| | | | | | | | | | | | | | 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.
* | Merge branch 'handleUnplug' into output-managementStivvo2020-10-311-1/+2
|\ \
| * | Fix crash unplugging a focused monStivvo2020-10-311-1/+2
| |/ | | | | | | | | Focus newmon, which we know for sure that it isn't be unplugged or disabled
* | Merge branch 'handleUnplug' into output-managementStivvo2020-10-310-0/+0
|\|
| * Focus client on a new monitor before closingStivvo2020-10-311-0/+1
| |\
* | | Block access to disabled monitorStivvo2020-10-301-4/+6
| | | | | | | | | | | | | | | Before this, pressing mod+comma or mod+period (focusmon function) moved the focus to disabed monitors. Now, all disabled monitors are skipped
* | | Move disabled clients to the leftStivvo2020-10-301-2/+2
| | | | | | | | | | | | To the nearest monitor to the left of the disabled one
* | | Merge branch 'handleUnplug' into output-managementStivvo2020-10-301-14/+10
|\ \ \
| * \ \ Merge branch 'handleUnplug' of http://olidata.stivvo01.com:3000/Stivvo01/dwl ↵Stivvo2020-10-301-0/+1
| |\ \ \ | | |/ / | |/| / | | |/ into handleUnplug
| * | Closemon(), newmon as parameterStivvo2020-10-301-15/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Actually move clients away from a disabled monStivvo2020-10-301-14/+3
| | | | | | | | | | | | | | | | | | 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.
* | | Merge branch 'handleUnplug' into output-managementStivvo2020-10-301-3/+3
|\ \ \ | | |/ | |/|
| * | Fix crash when unplugging a focused monitorStivvo2020-10-301-0/+1
| | | | | | | | | | | | Just focus a "safe" monitor before trying to to anything risky
| * | Cleaner if statementStivvo2020-10-301-3/+2
| |/
* | Merge branch 'output-management' of ↵Stivvo2020-10-251-1/+1
|\ \ | | | | | | | | | http://olidata.stivvo01.com:3000/Stivvo01/dwl into output-management