Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!princeton!udel!rochester!cornell!uw-beaver!teknowledge-vaxc!sri-unix!quintus!pds
From: pds@quintus.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Finishing up YAIP (Yet Another Input Handler), Need info.
Summary: better yet, how about executing a program?
Message-ID: <959@sandino.quintus.UUCP>
Date: 12 May 88 21:35:55 GMT
References: <8805090351.AA04051@cory.Berkeley.EDU> <1963@sugar.UUCP>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 19
Posted: Thu May 12 17:35:55 1988

In article <1963@sugar.UUCP>, peter@sugar.UUCP (Peter da Silva) writes:
> In article ... dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> > 	- Screen blanker after N1 seconds inactivity (def. 300 secs)
> 
> 	How about a screen dimmer?

Better yet, how about executing a program after timeout?  When the
program exits, assume something happened to signal that the screen
shouldn't be blanked anymore, and that the screen is the way it was when
the blanking prog was executed.  This would let anyone write their own
blank-screen routine to do whatever they like.  Someone could even
write a screen blanker that required a password to leave blank-screen
mode.  Doesn't seem like it would be any harder to execute a program
than to call a subroutine, the commandline parser would just have to be
fixed up.
-- 
-Peter Schachte
pds@quintus.uucp
...!sun!quintus!pds