dwl - dwm for Wayland

Age	Commit message (Collapse)	Author	Files	Lines
2020-10-31	Don't switch to another disabled monitors	Stivvo	1	-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-31	Fix crash with no monitors left	Stivvo	1	-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-31	closemon() has now only 1 parameter	Stivvo	1	-1/+1

2020-10-31	Don't switch to disabled mons after unplug	Stivvo	1	-1/+3

2020-10-31	Merge branch 'handleUnplug' into output-management	Stivvo	1	-8/+10

2020-10-31	Back to closemon() with one parameter	Stivvo	1	-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-31	Disable mon faster	Stivvo	1	-7/+3
	Since focusmon() now never focuses disabled monitors, there's no need to focus the disabled monitor first
2020-10-31	Fix crash when disabling focused mon	Stivvo	1	-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-31	Fix crash unplugging focused mon 2	Stivvo	1	-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-31	Merge branch 'handleUnplug' into output-management	Stivvo	1	-1/+2

2020-10-31	Fix crash unplugging a focused mon	Stivvo	1	-1/+2
	Focus newmon, which we know for sure that it isn't be unplugged or disabled
2020-10-31	Focus client on a new monitor before closing	Stivvo	1	-0/+1

2020-10-30	Block access to disabled monitor	Stivvo	1	-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-30	Move disabled clients to the left	Stivvo	1	-2/+2
	To the nearest monitor to the left of the disabled one
2020-10-30	Merge branch 'handleUnplug' into output-management	Stivvo	1	-14/+10

2020-10-30	Merge branch 'handleUnplug' of http://olidata.stivvo01.com:3000/Stivvo01/dwl ↵	Stivvo	1	-0/+1
	into handleUnplug
2020-10-30	Closemon(), newmon as parameter	Stivvo	1	-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
2020-10-30	Actually move clients away from a disabled mon	Stivvo	1	-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.
2020-10-30	Merge branch 'handleUnplug' into output-management	Stivvo	1	-3/+3

2020-10-30	Fix crash when unplugging a focused monitor	Stivvo	1	-0/+1
	Just focus a "safe" monitor before trying to to anything risky
2020-10-30	Cleaner if statement	Stivvo	1	-3/+2

2020-10-25	Handle monitor enable	Stivvo	1	-2/+9

2020-10-25	Move clients away from a disabled monitor	Stivvo	1	-2/+10
	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-25	Merge branch 'handleUnplug' into output-management	Stivvo	1	-3/+12

2020-10-24	closemon()	Stivvo	1	-3/+12
	Separate oputput movement from cleanupmon
2020-10-24	Merge branch 'handleUnplug' into output-management	Stivvo	1	-4/+29

2020-10-24	Readme: achieve fullscreen + allow borderpx = 0	Stivvo	1	-2/+2

2020-10-18	fix compile error mixed declaration	Stivvo	1	-1/+1

2020-10-17	Move sgeom assignment	Guido Cella	1	-2/+1
	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-17	Implement the output management protocol	Guido Cella	1	-0/+81
	It allows clients such as wlr-randr to configure the display.
2020-10-17	Added support for natural scrolling	will	1	-0/+5

2020-10-17	Added basic tap-to-click for touchpad users	will	1	-0/+6

2020-10-14	Quit fullscreen on new x11 window	Stivvo	1	-3/+4
	After the removal of quitfullscreen() dwl wouldn't compile widh xwayland enabled because createnotifyx11 was still using the old function
2020-10-14	Delete quitfullscreen()	Stivvo	1	-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-10-08	Keep windows fullscreen after redraw	Stivvo	1	-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-10-08	Set fullscreen simpler	Stivvo	1	-4/+4

2020-09-16	use m->m (fullscreen on top of layers)	Stivvo	1	-1/+1

2020-09-15	Keep client tags on unplug	Stivvo	1	-1/+1
	When unplugging a monitor, each client is moved to the same tag number as before on the new monitor
2020-09-15	Handle monitor unplug	Stivvo	1	-16/+25
	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-12	Restore floating win position after mon add	Stivvo	1	-0/+18
	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-11	extract function and comment it	Guido Cella	1	-11/+18

2020-09-11	remove braces	Guido Cella	1	-2/+1

2020-09-11	fix multi monitors even more	Guido Cella	1	-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).
2020-09-10	fix typo	Guido Cella	1	-4/+4

2020-09-10	simplify	Guido Cella	1	-1/+1

2020-09-09	fix multi monitors further	Guido Cella	1	-3/+1
	Fix layer surfaces without an exculsive area by using the right x and y for the current monitor (by Stivvo).
2020-09-08	Made scalebox the way sway does it	Bonicgamer	1	-4/+5

2020-09-08	remove unneeded line	Guido Cella	1	-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.
2020-09-08	try to fix again	Guido Cella	1	-4/+1
	Calculate x and y of usable_area, not just width and heigth.
2020-09-08	fix multi monitors	Guido Cella	1	-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.