Ctrl-M is VK_RETURN and although I don't recall the precise circumstances some parts of the image got severely confused when that key was reported normally. If you would like to experiment with it, just remove the line in sqWin32Window.c that says:
/* Note: VK_RETURN is recorded as virtual key ONLY */ if(keyCode == 13) return 1;
I'd be interested in finding out if this is still an issue or not (there is a good possibility that this goes back all the way to the state-based primitives which had to use a mixture of keyDown/keyChar events to produce proper results).
Cheers, - Andreas
Michael Rueger wrote:
Hi all,
while debugging through some event handling on Windows it seems that ctrl-m is the only key (combination) that is not generating a keystroke event? See the low level key event log below. Explanations? Red herring pointers?
Thanks
Michael P.S. Haven't checked on other platforms
[keyDown '<tab>'] [keystroke '<tab>'] #(2 32815515 9 2 0 9 0 1) [keyUp '<tab>']
#(2 32819187 17 1 2 17 0 1) [keyDown '<Ctrl-q>'] pressing the ctrl key #(2 32819890 77 1 2 77 0 1) [keyDown '<Ctrl-M>'] #(2 32819968 77 2 2 77 0 1) [keyUp '<Ctrl-M>'] #(2 32820515 17 2 0 17 0 1)