Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!hubcap!rchampe
From: rchampe@hubcap.UUCP (Richard Champeaux)
Newsgroups: comp.sys.amiga
Subject: Re: AMIGA Keyboard Buffer
Message-ID: <1330@hubcap.UUCP>
Date: 7 Apr 88 17:40:11 GMT
References: <3194@gryphon.CTS.COM>
Organization: Clemson University, Clemson, SC
Lines: 27

In article <3194@gryphon.CTS.COM>, bilbo@pnet02.cts.com (Bill Daggett) writes:
> 
> If I doze off while reading some of these exciting posts and wake up only to
> find my finger pushing down the spacebar I have successfully loaded up the
> Amiga's keyboard locally and can't stop the bit stream (until all the spaces
> in the buffer are used up).  This has happened twice and I have hung-up twice
> to avoid loosing out.  IS THERE any way to reset the buffer, or empty it?  And
> if not presently, could something be devised, i.e., is it possible?  No, DEL
> did nothing.  The bit stream kept on coming non-stop.
> 
> Bill
> 
     A simmilar thing has happened to me many times.  I have preferences set
up for a maximum key repeat speed.  This works just great for CLI and other
programs, but when I use one of the slower word processors, it causes all
kinds of problems.  Often have I held down the backspace key to delete a 
sentence, only to watch in horror as it continues to backspace over three pages
of text after I release the key.  Now, I think that dynamically allocated
buffers for I/O are just great, but there should be a way to limit
it for the keyboard.  A limit (perhaps user definable through preferences)
of about 100 characters should be sufficient for a keyboard.
I would think it would be a rare occurance for a user to need to buffer up
over 100 keystrokes (certainly not a 1000 or more) before they are processed.

Rich Champeaux
Clemson University

P.S.  This problem also causes sudden deaths when playing Hack.