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
First, let me thank you for the EMU webApp, you are doing amazing work!
I have (had) some problems with the keyboard shortcuts of the web app. For example, the "Shrink / Expand Selected Segment" shortcuts are not working for me. The problem is that I use the U.S. keyboard layout, so I get my plus sign ("+") by pressing Shift=. So for what the App says is "Shift + +" I had to press Shift7 which is the *-symbol on the US layout.
When looking into the config file default_emuwebappConfig.json I see that the ASCII-Codes are mapped to the different functionalities, so I changed them and now it works (I use = so ASCII 61 for expand left and +/ASCII 43 for expand right). But that change breaks the functionality for other layouts.
Would it may be possible to use the keyCodes instead of ASCII codes? That way the keys stay the same in different keyboard layouts.
The text was updated successfully, but these errors were encountered:
First, let me thank you for the EMU webApp, you are doing amazing work!
I have (had) some problems with the keyboard shortcuts of the web app. For example, the "Shrink / Expand Selected Segment" shortcuts are not working for me. The problem is that I use the U.S. keyboard layout, so I get my plus sign ("+") by pressing Shift=. So for what the App says is "Shift + +" I had to press Shift7 which is the *-symbol on the US layout.
When looking into the config file
default_emuwebappConfig.json
I see that the ASCII-Codes are mapped to the different functionalities, so I changed them and now it works (I use = so ASCII 61 for expand left and +/ASCII 43 for expand right). But that change breaks the functionality for other layouts.Would it may be possible to use the keyCodes instead of ASCII codes? That way the keys stay the same in different keyboard layouts.
The text was updated successfully, but these errors were encountered: