[RFC wayland-protocols v2] Screensaver/blanking inhibition
Bryce Harrington
bryce at osg.samsung.com
Tue Nov 24 22:49:46 PST 2015
A "screensaver inhibition protocol" is on the set of needed enhancements
for Wayland. This should turn off screen blanking and any running
screensaver for a period, then re-enabling it later.
An obvious use case is giving presentations. Other use cases include
games, kiosk, automotive infotainment systems.
I'd like to take a shot at defining the protocol for this and
implementing it for Weston. The design I have in mind mostly follows
xdg-screensaver and the DBUS screensaver API[1], which provide a
desktop-neutral 'inhibit' mechanism to temporarily disable the
screensaver/screenblanker on a per-process basis, except that it will be
per-surface instead of per-process.
So, after issuing the inhibit request for a surface, the screensaver
(and screenblanking) will be blocked until the surface is destroyed,
disabled, or otherwise loses visibility or becomes occluded.
---
v2: Stripped away most of the extraneous ideas. So this is now strictly
just the inhibition request, which affects only the display(s) the
surface is actually visible on.
Bryce Harrington (1):
Add screensaver inhibition protocol
Makefile.am | 1 +
unstable/screensaver-inhibit/README | 4 ++
.../screensaver-inhibit-unstable-v1.xml | 80 ++++++++++++++++++++++
3 files changed, 85 insertions(+)
create mode 100644 unstable/screensaver-inhibit/README
create mode 100644 unstable/screensaver-inhibit/screensaver-inhibit-unstable-v1.xml
--
1.9.1
More information about the wayland-devel
mailing list