Hi all,
VZ (from wxWindows) wrote:
Hello, I've decided to change wxMSW CHAR event generation
code to _not_ set Ctrl and Alt modifiers...
As wxPython user, I'm not a regulary wxDev-list reader. I
fell by chance on your comment.
I am very happy to hear about the AltGr key problem. You are
right in saying, there is a trap in theAltGr. The trap is
even more vicious: it is not enough to check if CtrlDown
and/or AltDown is true/false, your have to check the Ctrl
key status BEFORE the Alt status.
wxPython programmers are often falling in the same trap I
react as much and as often I can. See:
http://wiki.wxpython.org/index.cgi/CharacterCodesAndKeyboard
I was (and I am still) thinking there is some kind of
'basic' error in the key handling under MS windows
platforms.
From a wxPython side, I would say that if the problem is
solved at the wxWindows level, it should automatically be
solved on the wxPython level. There are so many wxPython
apps no working in my non US keyboard.
As I said many times on the wxPython list, at present date
the final test is Ctrl+Alt+e, or AltGr+e or Alt+0128 (from
numeric pad). With this keys combination, you should get
the euro symbol. If this is not working, it sounds like
"Houston, we have a problem..."
Hope for a great success.
Regards
Jean-Michel Fauth, Switzerland