clyde@ut-ngp.UUCP (03/02/87)
Could the X designers (or anybody else who feels up to it) explain the seemingly useless behavior of the X 'screen saver' function. If you run ANYTHING which updates the window (e.g. xclock, xload), then the screen saver doesn't work. This behavior I can understand - it's just like the screen saver on a conventional terminal. But for the screen saver to work, the server must be TOTALLY IDLE - if there is any client which EVER talks to the server, even if the screen is NOT changed, the screen saver is turned off. What makes sense to me is that the screen saver should be triggered by USER inaction, i.e. If I don't touch the keyboard or mouse for 10 minutes, my screen should be blanked. I know this is a bit more complicated to do, but makes more sense to me. Sigh. I guess I have to do an X version of 'lockscreen'. -- Shouter-To-Dead-Parrots @ Univ. of Texas Computation Center; Austin, Texas clyde@ngp.cc.utexas.edu; ...!ut-sally!ut-ngp!clyde "It's a sort of a threat, you see. I've never been very good at them myself, but I've told they can be very effective."
RWS@ZERMATT.LCS.MIT.EDU.UUCP (03/03/87)
What makes sense to me is that the screen saver should be triggered by USER
inaction, i.e. If I don't touch the keyboard or mouse for 10 minutes,
my screen should be blanked. I know this is a bit more complicated to
do, but makes more sense to me.
That's the way it works in Version 11.radzy@Sun.COM@unet.UUCP (03/03/87)
> What makes sense to me is that the screen saver should be triggered by USER > inaction, i.e. If I don't touch the keyboard or mouse for 10 minutes, > my screen should be blanked. I know this is a bit more complicated to > do, but makes more sense to me. > >That's the way it works in Version 11. I prefer it the way it is in V10. This gives me the ability to notice things when they happen, rather than finding surprises when I first do something. Would it be possible for the developement team to make this an option? I should be set under software control, and people could put an entry in their .uwmrc (or whatever other configuration file) of the form: screensaver={keyboard|text|any} This would un-saver ( :-) the screen when 1. Any keyboard (or mouse) event happend. 2. Any text is sent to any open window. 3. Any screen change. respectively. There could also be an option "off", so that the screen saver feature would never be initiated. PS I have a working screen lock program, which I intend to post to net.sources and to this mail group sometime next week. I still need to write a manual page for it, though. ***************************************************************** -- Tim "radzy" Radzykewycz The Incredible Radical Cabbage radzy@unet.uucp -- [oliveb|sunncal] !unet!radzy
jg@jumbo.UUCP (03/03/87)
The V10 screen saver was trivial to implement with no overhead. Feel free to fix it.... The V11 implementation only triggers screen saver on lack of keyboard and mouse input. "Fixed in next major release" Jim Gettys