TinyTERM’s keyboard mapper allows you to remap the NumLock key. Version 4 also has a Force Num Lock on setting that will keep NumLock on for the TinyTERM window.

Doing both of these on a Windows NT, 2000, XP, 2003 or Vista system causes a particular issue. When you hit the remapped NumLock key, it repeats the mapped action three times.

Those operating systems read both the key press and the key release as separate events. TinyTERM also reads the key press as an event. So what actually happens is that the mapped action is triggered once for each event.

If the NumLock key is not mapped in TinyTERM, there is no problem with the Numlock signal being processed more than once. But altering TinyTERM’s behavior for this would damage other keyboard mapping functions.

CR 231

This entry was posted on Wednesday, March 14th, 2007 at 2:01 pm and is filed under Keyboard, Windows. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.