Skip to main content

Hi everyone.  This is more for your information than a question.   Since the manual says the KEYSTROKE table is maximum of 170 entries, and I was having some issues, I wondered if the table updated existing entries when a key was changed, or if it was just a log which the runtime searched to see the most recent entry.   I did some testing and table entries get updated so it's not a "log", it's a table.

I built a little program to test input and exception keys.  I added a loop to set/reset the kr key back and forth between two values.  Did that 100 times for 200 entries into the table.  Set the kr one more time after the loop, and that's the value I got.  So the table updates entries for various keys, it's not a log where you read everything to find the most recent change.

Hi everyone.  This is more for your information than a question.   Since the manual says the KEYSTROKE table is maximum of 170 entries, and I was having some issues, I wondered if the table updated existing entries when a key was changed, or if it was just a log which the runtime searched to see the most recent entry.   I did some testing and table entries get updated so it's not a "log", it's a table.

I built a little program to test input and exception keys.  I added a loop to set/reset the kr key back and forth between two values.  Did that 100 times for 200 entries into the table.  Set the kr one more time after the loop, and that's the value I got.  So the table updates entries for various keys, it's not a log where you read everything to find the most recent change.

As I said, this is info, so I'll "answer" this myself - yes, a new keystroke variable entry for a key, replaces the old one. 

Terms & ConditionsAccessibility statement