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
Disclaimer: I was not able to test this, because I don't have my ErgoDox yet.
My plan is to connect my ErgoDox and another standard keyboard to my PC. The OS will be configured to use querz (German layout), because people coming to my desktop shall be able to type. The ErgoDox should allow me to type in my layout of choice (http://neo-layout.org).
If I understand correctly from inspecting the source code, there are some issues when the keyboard is connected to a PC using a non-US layout:
First of all, the neo layout does support some chars, that are not available on the standard querz keyboard. Therefore I would use the key_function type_string. This method tries to send key codes for all the chars available on a standard ansi keyboard. But that will result in wrong keycodes being send for these chars: "[Groovy, Baby]" with the keyboard attached to a German PC will send "üGroovz, Babz+". Workaround: Only use that method for chars that are not on a US keyboard.
Second: I need to define the layout using the US layout in mind, to get the correct char when pressing a particular key. E.g. when pressing the key where there would be a "z" on a German keyboard ("y" on a US keyboard), I really want it to be an "ü". To get an "ü" when the OS thinks the keyboard uses the German layout, it has to send the keycode for "[" on a US keyboard.
It should be easy to define the desired outcome without having to think in respect to the US layout. There should be some #define statement to set the target language code, and then I want to be able to just type what each key should produce.
The text was updated successfully, but these errors were encountered:
Not entirely sure what the issue is... I hope you'll forgive me for not being able to read carefully and respond thoroughly, as school just started, and I'm super busy. See my comment for #36 too though. I have a feeling the two issues are caused by the same thing (i.e. the USB HID standard for boot keyboards).
Disclaimer: I was not able to test this, because I don't have my ErgoDox yet.
My plan is to connect my ErgoDox and another standard keyboard to my PC. The OS will be configured to use querz (German layout), because people coming to my desktop shall be able to type. The ErgoDox should allow me to type in my layout of choice (http://neo-layout.org).
If I understand correctly from inspecting the source code, there are some issues when the keyboard is connected to a PC using a non-US layout:
First of all, the neo layout does support some chars, that are not available on the standard querz keyboard. Therefore I would use the key_function type_string. This method tries to send key codes for all the chars available on a standard ansi keyboard. But that will result in wrong keycodes being send for these chars: "[Groovy, Baby]" with the keyboard attached to a German PC will send "üGroovz, Babz+". Workaround: Only use that method for chars that are not on a US keyboard.
Second: I need to define the layout using the US layout in mind, to get the correct char when pressing a particular key. E.g. when pressing the key where there would be a "z" on a German keyboard ("y" on a US keyboard), I really want it to be an "ü". To get an "ü" when the OS thinks the keyboard uses the German layout, it has to send the keycode for "[" on a US keyboard.
It should be easy to define the desired outcome without having to think in respect to the US layout. There should be some
#define
statement to set the target language code, and then I want to be able to just type what each key should produce.The text was updated successfully, but these errors were encountered: