[issue22408] Tkinter doesn't handle Unicode key events on Windows

2014-09-23 Thread Terry J. Reedy
Terry J. Reedy added the comment: The term 'dead key' is new to me. I found this: https://en.wikipedia.org/wiki/Dead_key . 'AltGr' is also new: https://en.wikipedia.org/wiki/AltGr_key . It apparently is a 'modifier' key, not a 'dead key'. Standard non-Mac US keyboards apparently have

[issue22408] Tkinter doesn't handle Unicode key events on Windows

2014-09-23 Thread Ned Deily
Ned Deily added the comment: Just to avoid any confusion, Apple-supplied Mac keyboards don't have an AltGr key. It is found on certain PC keyboard layouts and, as such, could be used on any platform (Windows, OS X, or other Unix). -- ___ Python

[issue22408] Tkinter doesn't handle Unicode key events on Windows

2014-09-15 Thread Drekin
Drekin added the comment: It seems that it's a problem of dead key combinations rather than modifiers. Unicode characters produced directly (with or without modifiers) work correctly. Only one deadkey on my keyboard doesn't work at all. AltGr + M is a deadkey, but any following key is

[issue22408] Tkinter doesn't handle Unicode key events on Windows

2014-09-14 Thread Drekin
New submission from Drekin: Key events produced on Windows handles Unicode incorrectly when Unicode character is produced by dead-key combination. On my keyboard, (AltGr + M, a) produces several key events, last of which contains char==a, however, it should contain ∀. Also dead-key sequence

[issue22408] Tkinter doesn't handle Unicode key events on Windows

2014-09-14 Thread Ned Deily
Ned Deily added the comment: I don't have a real Windows setup to test but I would guess this may be Tk behavior. Perhaps the Tk wiki page on platform-specific keyboard modifier behaviors will help: http://wiki.tcl.tk/28331 -- nosy: +ned.deily