aboutsummaryrefslogtreecommitdiffhomepage
path: root/dwl.c
AgeCommit message (Collapse)AuthorFilesLines
2020-12-19remove goto when the border is 0Guido Cella1-3/+0
Rendering 0-dimension rectangles no longer crashes wlroots.
2020-12-19remove useless assignmentGuido Cella1-1/+0
calloc already initializes ints to 0.
2020-12-19s/maprequest/mapnotifyGuido Cella1-4/+4
This should be consistent with other function names instead of keeping the X name.
2020-12-19Added support for natural scrollingwill1-0/+5
2020-12-19Added basic tap-to-click for touchpad userswill1-0/+6
2020-12-19Made scalebox the way sway does itBonicgamer1-4/+5
Scaling a wlr_box without rounding can sometimes make the borders not connected and nice. I noticed this when setting scale in monrules to 1.2 So I've went and copied what Sway did in desktop/output.c but without having a second function and now using a random rounding macro I found on the internet so as to not use round from math.h.
2020-12-19s/prev/oldGuido Cella1-9/+9
Be consistent with the rest of the code and dwm
2020-12-19remove togglefullscreen keybindingGuido Cella1-8/+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.
2020-12-19Readme: achieve fullscreen + allow borderpx = 0Stivvo1-2/+2
2020-12-19Quit fullscreen on new x11 windowStivvo1-3/+4
After the removal of quitfullscreen() dwl wouldn't compile widh xwayland enabled because createnotifyx11 was still using the old function
2020-12-19Delete quitfullscreen()Stivvo1-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-12-19Keep windows fullscreen after redrawStivvo1-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-12-19Set fullscreen simplerStivvo1-4/+4
2020-12-19use m->m (fullscreen on top of layers)Stivvo1-1/+1
2020-12-19fix typoGuido Cella1-4/+4
2020-12-19Allow borderpx = 0Stivvo1-2/+2
2020-12-19Toggle fullscreen on all clientsStivvo1-3/+18
mod+e allows to toggle fullscreen any client, even those who don't support it themselves
2020-12-19Handle new windowsStivvo1-2/+22
Windows lose fullscreen state when a new window is created in the same tag
2020-12-19isfullscreen intStivvo1-4/+5
2020-12-19Same fscreen func for xdg and xwaylandStivvo1-32/+14
2020-12-19Fullscreen xwaylandStivvo1-1/+31
2020-12-19Unlink fullscreenStivvo1-0/+1
2020-12-19Restore windows after fullscreenStivvo1-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-12-19No borders on fullscreen windowsStivvo1-1/+8
Some code has been borrowed from the smartBorders patch
2020-12-19Toggle fullscreenStivvo1-1/+1
2020-12-19Basic fullscreenStivvo1-0/+11
2020-12-19handle the x11 configure eventGuido Cella1-0/+13
This fixes the window size of old games in Wine.
2020-12-19implement the virtual keyboard protocolGuido Cella1-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.
2020-12-19Allow toggling the layout before selecting a different oneGuido Cella1-1/+2
2020-12-19Implement the idle protocolGuido Cella1-0/+12
It allows clients such as swayidle and chat applications to monitor user idle time.
2020-12-19deactivate focused client when spawning a new oneGuido Cella1-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.
2020-12-19implement the wlr-data-transfer protocolGuido Cella1-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.
2020-12-19fix temporarily disabling a single monitorGuido Cella1-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.
2020-10-31Don't switch to another disabled monitorsStivvo1-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()
2020-10-31Fix crash with no monitors leftStivvo1-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
2020-10-31closemon() has now only 1 parameterStivvo1-1/+1
2020-10-31Don't switch to disabled mons after unplugStivvo1-1/+3
2020-10-31Merge branch 'handleUnplug' into output-managementStivvo1-8/+10
2020-10-31Back to closemon() with one parameterStivvo1-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.
2020-10-31Disable mon fasterStivvo1-7/+3
Since focusmon() now never focuses disabled monitors, there's no need to focus the disabled monitor first
2020-10-31Fix crash when disabling focused monStivvo1-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)
2020-10-31Fix crash unplugging focused mon 2Stivvo1-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.
2020-10-31Merge branch 'handleUnplug' into output-managementStivvo1-1/+2
2020-10-31Fix crash unplugging a focused monStivvo1-1/+2
Focus newmon, which we know for sure that it isn't be unplugged or disabled
2020-10-31Focus client on a new monitor before closingStivvo1-0/+1
2020-10-30Block access to disabled monitorStivvo1-4/+6
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 leftStivvo1-2/+2
To the nearest monitor to the left of the disabled one
2020-10-30Merge branch 'handleUnplug' into output-managementStivvo1-14/+10
2020-10-30Merge branch 'handleUnplug' of http://olidata.stivvo01.com:3000/Stivvo01/dwl ↵Stivvo1-0/+1
into handleUnplug
2020-10-30Closemon(), newmon as parameterStivvo1-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