Shortcut numbers no longer show conflict message

[zacjansheski]

Issue type

Choose option...

Description with steps to reproduce

1. In Preferences > Shortcuts add a shortcut that is a number
2. Before 4.5, a conflict message was shown "Enter TAB: fret x"
3. Now no message is shown, when trying to use the new shortcut, duration will change

Supporting files, videos and screenshots

4.4.4

4.5

What is the latest version of MuseScore Studio where this issue is present?

OS: macOS 15.3, Arch.: arm64, MuseScore Studio version (64-bit): 4.5.1-250800846, revision: github-musescore-musescore-603eca8

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

MacOS15

Additional context

Pre 4.5 behavior is expected, but I believe the more common "Set Duration" conflict would be preferred

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[bkunda]

Looks like a pre-condition for this might be that the numeric shortcut has to not already be (re-)assigned to something else.

For example, if I re-assign a command to a numeric shortcut, then the conflict label suddenly re-appears. But if it's not been re-assigned, then it won't.

Screen.Recording.2025-03-31.at.6.52.10.am.mov

I think this reduces the severity somewhat, because it's not every shortcut overwrite that's being affected here (and the action remains reversible too).

[bkunda]

Investigated this a bit further. It's a tad complicated, but I can reproduce this in 4.3.2, and @mathesoncalum can reproduce something similar in 4.2.

If you try to assign a numerical key shortcut to a command that already contains a shortcut assignment, AND that numerical key shortcut is already assigned to another command, then the conflicting shortcut message will show.

If, however, you try to assign such a numerical key shortcut to a command that has no shortcut assignment, then no conflicting shortcut message will show.

It is, however, possible to still trigger the conflicting shortcut message in this situation by re-assigning the numerical key shortcut to a command where the conflicting shortcut message does show. If this is done first, then that same numerical shortcut can be re-assigned to a command that has no shortcut assignment, where the conflicting shortcut message will now show as expected.