Re: KEYTIME? Message #9 Posted by James M. Prange (Michigan) on 11 Sept 2007, 10:18 p.m., in response to message #6 by Dan Greil
The 49g+ AUR is correct for early 49g+ ROM revisions, but incorrect for recent ROM revisions
The KEYTIME\-> and \->KEYTIME commands were indeed "resurrected" in the 49g+, although I don't recall with which ROM revision. I suppose that the ROM revision could be found with a search of the comp.sys.hp48 usenet group.
The ROMs intended for the 49G have working keytime commands, but that model has little, if any, problem with doubled keystrokes due to key bounce, and having the keytime value set too high can cause missed keystrokes. The default value (1365) seems too high for most users.
When the 49g+ was first released, its ROM didn't have working keytime commands; after all, they seemed to be more trouble than they were worth in the 49G. But it soon became all too obvious that the keyboard on the 49g+ has various problems, sometimes including missed or doubled keystrokes, so at some ROM revision, the keytime commands were made active again.
The 50g has active keytime commands, unless it's been flashed it with an early 49g+ ROM.
The keytime value is the number of ticks (1 second = 8192 ticks) that a repeated press of the same key will be ignored for, with a range of 0 through 4096.
KEYTIME\-> returns the current keytime value as a "real number".
\->KEYTIME takes a real or zint (exact integer) for an argument, and sets a new keytime value. \->KEYTIME rounds fractional arguments to integer values, treats negative arguments as 0, and arguments over 4096 as 4096.
With ROM version G revision 2.10-7 (and, I believe, other ROMs intended for the 49g+ or 50g that have active keytime commands), the default keytime value is 1138 (ticks), or somewhat over 1/8 second, which seems rather high. I recommend setting the keytime much lower, perhaps 256 (1/32 second), and actually, my 50g seems to work just fine with it set to 0.
Regards, James
|