41CL/Time Module "Correct" doesn't?

[BobVA]

(09-26-2014 09:27 PM)Joe Horn Wrote:  ..."The longer you wait to execute CORRECT, the smaller the error due to keystroke variation becomes ...

The time module manual also has an interesting footnote:

Quote: Approximately +/- 0.1 second is the maximum keystroke precision for most users. You can reduce precision error by executing CORRECT as a function assigned to a key instead of by XEQ ALPHA CORRECT ALPHA. This is because the calculator takes less time to internally locate and execute a function assigned to a single key.

Which is what I did.

I'm not sure what effect the TURBO setting on the CL might have on this, but I believe the speedup is disabled for actions related to the keyboard, so I'm guessing none, regarding that particular delay.

Bob