Why does Zap sometimes fail to take notice of Shift and Ctrl?
Zap must wait until it is told about the keypress before it can attempt to distinguish between various different key combinations which produce the same character codes, eg. Ctrl-A and Shift-Ctrl-A, Return and Shift-Return, Ctrl-H and Backspace. If an application decides that it needs to single-task for even a few seconds, it may happen that you release the keys fractionally too early (Zap thinks that they’re not being pressed) or that you press another key before Zap has processed the previous one. (It’s worth mentioning that Zap doesn’t check for ambiguities where there can be none, eg. when it’s told that you’ve pressed a function key.) The problems can be fixed, for Zap at least, by using the DeepKeys module, which logs Shift, Ctrl and Alt keypresses and also the key to which they apply. If you have problems with this module, we’d like to hear about them 🙂 Before Zap started using DeepKeys, it used another module named KeyboardExtend; this provided much the same functionality but
