Hi folks,
I'd like to use C::B 20.03 (on Win10) with different key bindings than the default ones. E.g. I'd like to use the key combination AltGr-D for doing something special. With C::B 16.01 this was working but with the new version it does not. Within the Keyboard shortcuts editor and assigning that key combination (AltGr-D) is shown as Ctrl-Alt-D but later on that combination does only work when I press Ctrl-Alt-D (and not AltGr-D). Does anybody know how to fix that? I'm already trying to debug that with a self compiled version but I haven't figured it out yet ...
Greetings Christoph
P.S.: Other AltGr-combinations won't work as well
I investigated this a bit, and it does seem to be a wxWidgets/MSW bug...
They say, that altgr == ctrl + alt doc and this works also for creating the key binding, but it seems that the accelerator table does not honer this, because the altgr key is not handled like a ctr + alt key in the accelerator table (this is managed by windows)....
I think the old key binder plugin was looking at the "character" that the keypress represented, and the new plugin looks at the keycode... but this is pure speculation
@pecanh Do you have an idea about this?
bluehazzard is correct in his analysis regarding the KeyBinder changes.
Do any of the following help to re-establish that AltGr sends ctrl-alt ?
https://superuser.com/questions/1225911/how-to-remap-the-alt-gr-key-on-windows
https://www.thewindowsclub.com/how-do-i-enable-or-disable-alt-gr-key-on-windows-10-keyboard
I have no way of testing AltGR on my system.
@pecan Isn't testing this a matter of just choosing a keyboard layout in the settings which has the altgr key in it and which matches also your hw keyboard layout?
I think testing is not the point... as far as i understand the issue is in the microsoft accelerator table that does not handle altgr events correctly...
so this ticket is probably a "cant-fix"