Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!snorkelwacker!usc!rutgers!mephisto!prism!gt5784a
From: gt5784a@prism.gatech.EDU (Walter G. Reynolds (JJ))
Newsgroups: comp.sys.amiga.tech
Subject: Re: Why doesn't RETURN repeat?
Summary: because of the keymap
Message-ID: <12265@hydra.gatech.EDU>
Date: 7 Aug 90 00:05:08 GMT
References: <1990Aug4.191910.27922@msuinfo.cl.msu.edu> <35206@ut-emx.UUCP> <26778@pasteur.Berkeley.EDU> <1990Aug6.180013.2583@ux1.cso.uiuc.edu>
Distribution: usa
Organization: Georgia Institute of Technology
Lines: 38

In article <1990Aug6.180013.2583@ux1.cso.uiuc.edu> ja26612@uxa.cso.uiuc.edu (Pogo Joe) writes:
>navas@sim.uucp (David C. Navas) writes:
>
>>>>Why do all the keys repeat except for the RETURN?
>>>
>>I believe key repeating is handled by the input handler and is user-customizable
>>via keymaps.
>

From page 305 of the original Rom Kernal Manual: Libraries and devices:

REPEATABLE BIT TABLE
--------------------

For both the low and high keymaps there is an 8 byte table that provides
one bit per possible raw keycode.  This bit indicates whether or not the
specified key should repeat at the rate set by the preferences program.
The bit positions correspond to those specified in the capsable bit table.

If there is a 1 in a specific position, the key can repeat.  The vectors 
that point to these tables are called km_LoRepeatable and km_HiRepeatable.



I hope that this answers your question!

(in English, the Keymap defines whether or not any key can repeat.  The
model of the computer doesn't matter)

Walter (JJ) Reynolds



-- 
This .signature is being released as ShareWare.  This means that if you
like it, you are morally obligated to send your .signature to me in
return.  Send your .sigs to: gt5784a@prism.gatech.edu.  Any donations
will be used for future .sig releases.