Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!mips!news.cs.indiana.edu!ux1.cso.uiuc.edu!bradley.bradley.edu!buhub!guru
From: guru@buhub.bradley.edu (Jerry Whelan)
Newsgroups: comp.sys.handhelds
Subject: Re: HP48 Auto-Off procedure?
Keywords: hp48, off
Message-ID: <1991May15.015715.16582@bradley.bradley.edu>
Date: 15 May 91 01:57:15 GMT
References: <282efa57:3081comp.sys.handhelds@hpcvbbs.UUCP> <3515@charon.cwi.nl> <22680@shlump.lkg.dec.com>
Sender: news@bradley.bradley.edu
Organization: Bradley University
Lines: 17
Nntp-Posting-Host: buhub.bradley.edu

In article <22680@shlump.lkg.dec.com> edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.)) writes:

-} alarm, and schedule a new one.  One annoying thing is that searching for
-} alarms is not completely simple -- one has to match the object in the
-} alarm, since other alarms may have the same time, and the index may
-} change if other alarms are activated or set.  Another annoying thing is
-} that this will consume time every time the user presses ENTER.

	Rather than updating the alarm, you might want to use a flag to
signify off-ability.  For a 5 minute auto-shut off, you would schedule
the alarm every 2.5 minutes.  It would check the flag and if 1, set it
to 0 and if 0 shut the calculator down.  The vectored-entry function would
always set the flag to a 1.  This isn't perfect, but it would probably
be much faster.
-------------------------------------------------------------------------------
	"I'm not sure what I mean, so I'm going to listen to what I say."
 guru@ (buhub.bradley.edu || bucc1.bradley.edu) || whelan@wiliki.eng.hawaii.edu