summaryrefslogtreecommitdiff
path: root/dwl.c
AgeCommit message (Collapse)Author
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-31Focus client on a new monitor before closingStivvo
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-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-24closemon()Stivvo
Separate oputput movement from cleanupmon
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-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).
2020-09-10simplifyGuido Cella
2020-09-09fix multi monitors furtherGuido Cella
Fix layer surfaces without an exculsive area by using the right x and y for the current monitor (by Stivvo).
2020-09-08remove unneeded lineGuido Cella
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-08try to fix againGuido Cella
Calculate x and y of usable_area, not just width and heigth.
2020-09-08fix multi monitorsGuido Cella
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.
2020-09-06remove variableGuido Cella
2020-09-05use size_t for lengthsGuido Cella
2020-09-05rename variable and merge 2 linesGuido Cella
2020-09-05simplifyGuido Cella
2020-09-04use unsigned int for loop indexesGuido Cella
2020-09-04Don't let overlays lose focusGuido Cella
if you open a new window while an overlay is mapped, the overlay should stay focused
2020-09-04fix restoring pointer focusGuido Cella
I don't know why I thought it was working before. Maybe I should go do something else.
2020-09-04improve code styleGuido Cella
2020-09-04remove commentGuido Cella
I don't know why it wasn't working before but now it does ¯\(ツ)/¯ (it wasn't caused by the just removed code either)
2020-09-04remove mysterious codeGuido Cella
Why would a surface that's not keyboard interactive get focused? Let's remove this for now and see if issues arise.
2020-09-04focus the previous client in the similar code tooGuido Cella
2020-09-04refocus old clientGuido Cella
When a layer surface is destroyed focus should be returned to the last client. Luckily if there are multiple overlays the previous overlay still gets focused.
2020-09-04fix alhpabetical orderGuido Cella
2020-09-04simplify focus leave conditionGuido Cella
2020-09-04reuse motionnotify()Guido Cella
2020-09-04enable pointer on layer surfacesGuido Cella
2020-09-03more TODOsGuido Cella
2020-09-03fix focus leave conditionGuido Cella
needs refactoring and testing
2020-09-03send pressed keys to topmost layer surfaceGuido Cella
2020-08-29remove blank lineGuido Cella
2020-08-29don't handle failed callocGuido Cella
be consistent with the rest of the code
2020-08-29order variables more how like they are initializedGuido Cella
2020-08-28Reuse render() and struct timespec *nowGuido Cella
2020-08-27reuse m->mGuido Cella
2020-08-27remove commentGuido Cella
wlr_output_layout_get_box internally calls wlr_output_effective_resolution
2020-08-27set a monitor geometry only when creating itGuido Cella
Lets layers with an exclusive area shrink the usable area
2020-08-27render in the same order as swayGuido Cella
2020-08-26correct variable nameGuido Cella
2020-08-26rename functions tooGuido Cella
2020-08-26remove extra spaceGuido Cella
2020-08-26render layer surfacesGuido Cella
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-25 17:23:31 +0000