Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MU4] Crescendo shortcut not working on Italian keyboard layout #13586

Open
sberla365 opened this issue Oct 2, 2022 · 1 comment
Open

[MU4] Crescendo shortcut not working on Italian keyboard layout #13586

sberla365 opened this issue Oct 2, 2022 · 1 comment

Comments

@sberla365
Copy link

I am on Linux with Italian keyboard and I cannot trigger crescendo with the default shortcut. The shortcut is defined in Preferences as Shift+, but that combination does not work. When replacing the shortcut with the very same key combination, the program recognises it as the resulting character (which is ; on an Italian keyboard) and everything works well. Decrescendo shortcut is perfectly recognised.
I see that on an American keyboard the default key combinations produce the characters < and > which make more sense and are way more intuitive for crescendo and decrescendo. Being (I believe) < and > universal across languages and keyboard layouts, I think these shortcuts should be defined by the character rather than the key combination, so that it can be more universal. Just a thought since I don't really know the technicality of programming and shortcuts.

I had similar issues with other shortcuts (I cannot remember exactly which one now) which were also defined by the key combination and did not work but they worked when substituted with the very same key combination (also in those cases recognised as the resulting character and not by the combination).

What seems odd to me in all this is that some default shortcuts are defined by key combinations but when adding a custom one it is recognised by the character even when using the very same key combination of the default one.

@cbjeukendrup
Copy link
Contributor

What seems odd to me in all this is that some default shortcuts are defined by key combinations but when adding a custom one it is recognised by the character even when using the very same key combination of the default one.

It seems to me that this is an important problem, and I think it is what I encountered here: #11956 (comment)

@cbjeukendrup cbjeukendrup added this to To do in Keyboard navigation and shortcuts via automation Mar 4, 2023
@cbjeukendrup cbjeukendrup added the P2 Priority: Medium label Mar 4, 2023
@cbjeukendrup cbjeukendrup added this to To do in 4.x SHORTLIST via automation Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium
Development

No branches or pull requests

2 participants