Problems with Screensavers and other activity sensitive demons.
hp at redhat.com
Thu Jun 7 08:44:03 PDT 2007
William Jon McCann wrote:
> Yeah. And that I designed that interface in October 2004 (D-Bus 0.22)... :)
The interface is correct, don't worry about it ;-)
> Not that this really has much to do with Graeme's problem. If we had
> org.freedesktop.ScreenSaver.Inhibit() that might just do. However,
> the use case we may not be covering perfectly is: "watching a movie on
> one output when there are multiple outputs attached and the unused
> outputs should save power".
Inhibit() seems good enough to me to start. Add InhibitScreen() later to
solve the problem of inhibiting only one screen...
The only thing that seems hard about InhibitScreen() is identifying the
screen; a canonicalized display.screen name is probably good enough though.
More information about the xdg