diff options
| author |  Simon Ser <contact@emersion.fr> | 2023-07-12 10:14:15 +0200 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2023-07-19 09:28:33 +0200 |
| commit | ee4637b086aed256c7698b9f68786e6de5d8da00 (patch) | |
| tree | c55e185db2dd3be42484d24dd6edfe34906a0108 /README.md | |
| parent | swaynag: handle wayland-cursor failures (diff) | |
| download | sway-ee4637b086aed256c7698b9f68786e6de5d8da00.tar.gz sway-ee4637b086aed256c7698b9f68786e6de5d8da00.tar.zst sway-ee4637b086aed256c7698b9f68786e6de5d8da00.zip | |
Deprecate seat idle_wake
Sway has two knobs to control idling:
- seat idle_inhibit: when the seat is active (ie. not idle), this
extends the active state. When the seat is idle, this is
ignored.
- seat idle_wake: when the seat is idle, this wakes up the seat.
When the seat is active, this is ignored.
The motivation for the deprecation is two-fold:
- The concept of "seat idle state" is ill-defined. Each idle-notify-v1
client will pass a different idle timeout. With the old logic, a
seat was declared idle if and only if all idle-notify-v1 timeouts have
expired. However, if only a portion of the timeouts have expired,
then some clients would wake up, and the rest would stay active.
This is inconsistent with the definition of idle_inhibit/idle_wake:
idle_inhibit was used for clients which are waking up.
- It never worked properly with the new idle-notify-v1 protocol
and no-one noticed. Only the legacy KDE idle protocol is taken
into account, but that protocol is not used anymore.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions