aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Define monitor order with monrules[]Stivvo2020-12-212-4/+29
| | | | | | | | | | | | | | The order in which monitors are defined in monrules[] actually matters. Monotors that aren't configured in monrules[], it will always be the leftmost.
| * don't reset the cursor imageGuido Cella2020-12-211-1/+1
| | | | | | | | | | | | ...in internal calls to restore pointer focus. Necessary for the unclutter patch, and there's no harm in avoiding this call even in mainline; might prevents issues in same edge cases.
| * update README.mdGuido Cella2020-12-211-30/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - A maximum SLOC can't be reasonably determined before implementing the missing protocols, so not any time soon - dwl definitely isn't a simple as dwm since it must implement lots of Wayland protocols and not just manage windows. The status bar integration, layer shell popups, damage tracking and IME are gonna require hundreds more lines each. - "Buffering of input when spawning a client so you don't have to wait for the window (use `wl_client_get_credentials` to get the PID) - would this require passing through something like dmenu? Extension protocol?" This sounds exoteric, if anything this should be patch. - Can dwl really be started from within an X session? When I do it from dwm it crashes. - A window's texture is scaled for its "home" monitor only (noticeable when window sits across a monitor boundary) Gonna open a ticket for this rather than keep it in the README.
| * say TODOGuido Cella2020-12-201-8/+8
| | | | | | | | just wtf is XXX supposed to be? It sounds like a pornographic thing.
| * rename drwGuido Cella2020-12-201-9/+9
| | | | | | | | | | It's impossible to understand that this stands from drawable if you're not familiar with dwm's code.
| * don't notify of activityGuido Cella2020-12-201-4/+7
| | | | | | | | ...or update selmon when we just want to restore pointer focus.
| * deactivate the focused client on overlay focusGuido Cella2020-12-201-0/+2
| |
| * replace shouldfocusclients with checking oldGuido Cella2020-12-201-27/+24
| | | | | | | | And don't activate clients while an overlay is focused.
| * fix keyboard focus with overlaysGuido Cella2020-12-201-7/+8
| | | | | | | | | | | | | | Don't let internal calls to motionnotify(0) meant to update the pointer focus from maplayersurfacenotify and destroylayersurfacenotify also shift the keyboard focus to the surface under the cursor with sloppyfocus.
| * ensure that xwayland cursor defaults to left_ptrGuido Cella2020-12-201-0/+7
| | | | | | | | | | | | | | Don't show an X cursor when closing an Xwayland window or with certain dropdowns. Based on https://github.com/djpohly/dwl/pull/32
| * enable adaptive syncGuido Cella2020-12-201-0/+1
| | | | | | | | | | The comment in this function's declaration says the backend is free to ignore this setting, so maybe there's no need to make it configurable?
| * use boolGuido Cella2020-12-202-54/+56
| | | | | | | | | | Because it's 2020. Passing integers to wlroots variables and functions with bool in their signature is silly.
| * remove -Werror=declaration-after-statementGuido Cella2020-12-192-163/+151
| | | | | | | | | | | | wtf is the point of this crap? It makes the code harder to follow, increases the line count and made me fail compilation a million times. We shouldn't blindy follow everything about suckless's style.
| * remove goto when the border is 0Guido Cella2020-12-191-3/+0
| | | | | | | | Rendering 0-dimension rectangles no longer crashes wlroots.
| * remove useless assignmentGuido Cella2020-12-191-1/+0
| | | | | | | | calloc already initializes ints to 0.
| * s/maprequest/mapnotifyGuido Cella2020-12-191-4/+4
| | | | | | | | | | This should be consistent with other function names instead of keeping the X name.
| * add install target to Makefile and corresponding prefix variable to config.mkKeating9502020-12-192-0/+8
| |
| * tweak trackpad variablesGuido Cella2020-12-191-4/+4
| | | | | | | | | | Add static const and move them below in order to group the keyboard options.
| * Added support for natural scrollingwill2020-12-192-0/+6
| |
| * Added basic tap-to-click for touchpad userswill2020-12-193-1/+11
| |
| * remove log flags from readmeOyren2020-12-191-6/+0
| | | | | | | | | | | | The following commit has removed the logs but they are still in the readme. https://github.com/djpohly/dwl/commit/3b1992ca91b9a468019165c985263f5b1cc78c2c
| * Made scalebox the way sway does itBonicgamer2020-12-191-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.
| * s/prev/oldGuido Cella2020-12-191-9/+9
| | | | | | | | Be consistent with the rest of the code and dwm
| * 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()