Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!sol.ctr.columbia.edu!emory!gatech!purdue!haven!decuac!shlump.nac.dec.com!jareth.enet.dec.com!edp
From: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Newsgroups: comp.sys.handhelds
Subject: Re: (HP48SX)  Strange behavior...bug?
Message-ID: <21361@shlump.nac.dec.com>
Date: 22 Mar 91 15:54:56 GMT
References: <990@sousa.enet.dec.com>
Sender: newsdaemon@shlump.nac.dec.com
Reply-To: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Organization: Digital Equipment Corporation
Lines: 19

In article <990@sousa.enet.dec.com>, ervin@pinbot.enet.dec.com (Joseph
James Ervin) writes:

>\<< 1 10 FOR I DO UNTIL KEY END NEXT \>>
>
>This program should wait for 10 key presses, and leave the 10 keycodes
>on the stack.  Unfortunately, the actual number of key presses I must
>make tends to vary from 10 to as high as 14. 

It happens on my 48 (Revision E) as well.  I tried changing "DO UNTIL
KEY END" to "0 WAIT".  The problem vanishes then.  Perhaps KEY locks out
recognition of key presses briefly during its execution.

(BTW, you could use "START" instead of "FOR I" in the above.)


				-- edp (Eric Postpischil)
				"Always mount a scratch monkey."
				edp@jareth.enet.dec.com