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
Some keys on computer keyboard has two characters on them, I'll just call them "stacked keys" here for convenience, and use "top character" or "bottom character" to describe.
So combining it with shift key, we have following troubles:
Default hotkey mapping describes shift + stacked key shortcut in two different forms:
Form 1: shift with bottom char, like Shift + ., which is most commonly used;
Form 2: top char only, like +, for only a few shortcuts.
User defined hotkeys are always using the top char form, unless editing .xml files;
The two different forms for the same input can co-exist and cause problems.
Steps to reproduce
Problems demonstrated in video, using action "add accent":
[0:00 - 0:12] Try binding it to shift + up, text only shows 'up' with no shift. Back to score, shift + up still works as extending selection, and up itself still works as pitching up a semitone.
it won't work with up or shift + up anyway, even after I delete every hotkey bound to up and shift+up (not shown in video).
rebind it to up without pressing shift will make it work (not shown in video).
[0:16 - 0:25] Try binding it to shift + ., which is conflict with "add crescendo" by default. Text shows ">" in form 2, but since "add crescendo" is represented in form 1, there's no conflict warning, and neither "add accent" nor "add crescendo" works now.
[0:33 - 0:44] Try binding it to shift + =, which is conflict with "toggle sharp accident" by default. Both in form 2, so reassign warning is shown, and hotkey is properly reassigned.
Screenshots/Screen recordings
shift.key.problems.mp4
MuseScore Version
4.3.0
Regression
I don't know
Operating system
Windows 11 Pro, 22H2
Additional context
Default setting is binding multiple actions with up, and another binding to up key won't trigger conflict warning anyway.
The text was updated successfully, but these errors were encountered:
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
Some keys on computer keyboard has two characters on them, I'll just call them "stacked keys" here for convenience, and use "top character" or "bottom character" to describe.
So combining it with shift key, we have following troubles:
Shift + .
, which is most commonly used;+
, for only a few shortcuts.Steps to reproduce
Problems demonstrated in video, using action "add accent":
shift + up
, text only shows 'up' with no shift. Back to score,shift + up
still works as extending selection, andup
itself still works as pitching up a semitone.up
orshift + up
anyway, even after I delete every hotkey bound toup
andshift+up
(not shown in video).up
without pressing shift will make it work (not shown in video).shift + .
, which is conflict with "add crescendo" by default. Text shows ">" in form 2, but since "add crescendo" is represented in form 1, there's no conflict warning, and neither "add accent" nor "add crescendo" works now.shift + =
, which is conflict with "toggle sharp accident" by default. Both in form 2, so reassign warning is shown, and hotkey is properly reassigned.Screenshots/Screen recordings
shift.key.problems.mp4
MuseScore Version
4.3.0
Regression
I don't know
Operating system
Windows 11 Pro, 22H2
Additional context
Default setting is binding multiple actions with
up
, and another binding toup
key won't trigger conflict warning anyway.The text was updated successfully, but these errors were encountered: