[6121] in SIPB bug reports
Mark Eichin: Re: sun4 8.0I: xscreensaver
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Sep 10 00:33:29 1996
To: bug-sipb@MIT.EDU
Date: Tue, 10 Sep 1996 00:33:14 EDT
From: Greg Hudson <ghudson@MIT.EDU>
Someone may want to look into supporting this in the sipb locker. I'm
not sure if it's actually all that useful in the Athena environment,
but people ask for it periodically.
(No, as far as I know, none of the supported pltaforms support the
Xidle extension.)
------- Forwarded Message
Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po10.MIT.EDU (5.61/4.7) id AA13650; Tue, 10 Sep 96 00:08:24 EDT
Received: from cygnus.com by MIT.EDU with SMTP
id AA10736; Tue, 10 Sep 96 00:08:21 EDT
Received: from tweedledumb.cygnus.com (tweedledumb.cygnus.com [192.80.44.1]) by cygnus.com (8.6.12/8.6.9) with SMTP id VAA06721; Mon, 9 Sep 1996 21:08:16 -0700
Received: from maneki-neko.cygnus.com by tweedledumb.cygnus.com (4.1/4.7) id AA25818; Tue, 10 Sep 96 00:08:14 EDT
Received: (from eichin@localhost) by maneki-neko.cygnus.com (8.7.5/8.7.3) id AAA08544; Tue, 10 Sep 1996 00:08:13 -0400
Sender: eichin@cygnus.com
To: Greg Hudson <ghudson@MIT.EDU>
Cc: bugs@MIT.EDU
In-Reply-To: "[14620] in Athena Bugs"
Subject: Re: sun4 8.0I: xscreensaver
From: Mark Eichin <eichin@MIT.EDU>
Date: 10 Sep 1996 00:08:12 -0400
Message-Id: <xe13f0rdnbn.fsf@maneki-neko.cygnus.com>
Lines: 34
X-Mailer: Gnus v5.2.39/Emacs 19.34
FYI -- xautolock, ftp.x.org:/contrib/applications/xautolock.pl10.tz,
seems to do most of the work. (Not sure if any athena platforms
support the Xidle extension...)
quoting from the README...
HOW IT WORKS
============
If xautolock has been compiled to support Xidle, it first tries to
find out whether the X server also supports Xidle. If it does,
xautolock will periodically call xidle to determine the elapsed time
since the last input event, and will then base its actions upon that.
In the absence of Xidle, when it starts executing, xautolock
traverses the window tree, selects SubstructureNotify on all windows
and adds each window to a temporary list. About +- 30 seconds later,
it scans this list, and now asks for KeyPress events. However, it
takes care to interfere as little as possible with the event
propagation mechanism. This is the reason for the delay between the
moment xautolock learns about a new window (and consequently asks for
SubstructureNotify events) and the moment it asks for KeyPress
events. Whenever a new window is created by an application, a similar
process takes place. In contradiction to what many people believe,
this scheme does not cause a noticeable overhead.
In addition, xautolock periodically issues a QueryPointer request in
order to find out whether the pointer has moved and implement the
"corners" feature as decribed in the man page.
If nothing happens within a user-specified period of time, xautolock
will fire up a program which is supposed to lock the screen. While
this program is running, xautolock itself remains on the look-out for
user interaction.
------- End of Forwarded Message
