HP Forums
\->keytime (49g+) - Printable Version

+- HP Forums (https://archived.hpcalc.org/museumforum)
+-- Forum: HP Museum Forums (https://archived.hpcalc.org/museumforum/forum-1.html)
+--- Forum: Old HP Forum Archives (https://archived.hpcalc.org/museumforum/forum-2.html)
+--- Thread: \->keytime (49g+) (/thread-68493.html)



\->keytime (49g+) - Eric Lundgren - 02-02-2005

To the fellow who posted the convention for adjusting the keytime: I do not seem to be able to get any response using that on the 49g+...what am I doing wrong? Its a seemingly trivial operation..

I have done it on the 49g, however.


Have you considered...(was: \->keytime (49g+)) - Vieira, Luiz C. (Brazil) - 02-02-2005

Hi, Eric;

Maybe I'll post about the obvious, but there is no harm trying, right?

Have you considered using higher values? Based on what you mention, \-> KEYTIME gave you no response in the HP49G+, meaning it accepted the command and reacted differently. I did not test yet, but considering that the 49G+ is considerably faster than the 49G, you'd need higher values for KEYTIME return sensitive changes in the scan time.

Hope this helps a bit.

Cheers.

Luiz (Brazil)

Edited: 2 Feb 2005, 2:49 a.m.


Re: \->keytime (49g+) - James M. Prange (Michigan) - 02-02-2005

It seems to work as expected for me; the same on the 49g+ as on the 49G. But I've now noticed that values greater than 4096 are treated as 4096.

If you do 4096 \->KEYTIME and then KEYTIME\->, then it should return 4096, and a press of the same key again in less than 1/2 second should be ignored.

Of course, I don't recommend leaving it at 4096; probably something around 500 or less, depending on how fast you type. The 49G default of 1365 seems a bit high to me. Of course, if you don't get accidental duplication of keystrokes at all, you could just set it to 0.

Note that like all commands, these are case sensitive, so it should be \->KEYTIME, not \->keytime. Maybe use the RightShift CAT (over thr P key); both \->KEYTIME and KEYTIME\-> are in the catalogue.