aboutsummaryrefslogtreecommitdiff
path: root/sway/lock.c
AgeCommit message (Collapse)Author
2024-02-15Drop unnecessary includes from sway/server.hSimon Ser
2024-01-18container: Don't track outputsAlexander Orzechowski
The scene graph abstraction does this for us
2024-01-18scene_graph: Port ext_session_v1Alexander Orzechowski
2023-12-13input/seat: rename seat_set_exclusive_client()Simon Ser
2023-12-13input/seat: inline seat_set_exclusive_client() with NULL clientSimon Ser
2023-12-13input/seat: drop exclusive_clientSimon Ser
This was a input-inhibit concept.
2023-10-06Chase wlroots!4331Alexander Orzechowski
2023-07-31Rebase all cursors in handle_surface_mapookami
Fix swaylock showing transient cursor after locked.
2023-06-02lock: listen to the correct map signalKirill Primak
2023-06-02chore: chase wlroots map logic unificationKirill Primak
2023-02-10Introduce surface_{enter,leave}_output()Simon Ser
We can centralize all output-related surface events from there.
2023-01-18Send wl_surface.enter for ext-session-lock surfacesSimon Ser
2022-12-01sway/lock: handle mode in output commit handlerSimon Zeni
2022-11-11lock: fix crash on output destroySimon Ser
Closes: https://github.com/swaywm/sway/issues/7120
2022-10-28Rework session lock keyboard focus handlingDaniel De Graaf
When removing outputs, it is possible to end up in a situation where none of the session lock client's surfaces have keyboard focus, resulting in it not receiving keyboard events. Track the focused surface and update it as needed on surface destroy.
2022-04-29Implement ext-session-lock-v1Daniel De Graaf