this is now fixed. Minor clean-up resulting from my aborted refactoring of the keyboard event handling code.