Problems with Screensavers and other activity sensitive demons.
keithp at keithp.com
Thu Jun 7 13:16:29 PDT 2007
On Thu, 2007-06-07 at 11:44 -0400, Havoc Pennington wrote:
> The only thing that seems hard about InhibitScreen() is identifying the
> screen; a canonicalized display.screen name is probably good enough though.
With RandR version 1.2, we have names for displays, screens, crtcs and
outputs. The geometry of each crtc within the screen is defined so you
can tell which the movie is playing on and turn the others off.
Exposing DPMS controls per crtc (or per output) is on the list for RandR
1.3; help in defining the precise controls would be appreciated.
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/xdg/attachments/20070607/0be6d4fa/attachment.pgp
More information about the xdg