You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Qt swaps the Ctrl and the Cmd key, while wx does not. As a result, KeyEvent.control_down is set to different values for the same key press on the two backends
There is no flag for the Cmd key in KeyEvent
In wx, Cmd is mapped to '\x00' instead of 'Menu'
In wx, in a combination of Ctrl and letter, the 'key' attribute is set to a unicode instead of the letter. For example, Ctrl-C results in control_down=True (correct), but key='\x03' (should be u'c').
You can use this UI to have a look at KeyEvents in different toolkits, and to preview the proposed new behavior: https://gist.github.com/1310607
I'm about to submit a pull request from branch 'fix_ctrl_cmd' that should fix 1-4.
The text was updated successfully, but these errors were encountered:
There are a few issues with KeyEvent on Mac:
Qt swaps the Ctrl and the Cmd key, while wx does not. As a result, KeyEvent.control_down is set to different values for the same key press on the two backends
There is no flag for the Cmd key in KeyEvent
In wx, Cmd is mapped to '\x00' instead of 'Menu'
In wx, in a combination of Ctrl and letter, the 'key' attribute is set to a unicode instead of the letter. For example, Ctrl-C results in control_down=True (correct), but key='\x03' (should be u'c').
You can use this UI to have a look at KeyEvents in different toolkits, and to preview the proposed new behavior:
https://gist.github.com/1310607
I'm about to submit a pull request from branch 'fix_ctrl_cmd' that should fix 1-4.
The text was updated successfully, but these errors were encountered: