Open zacjansheski opened 2 weeks ago
Does not reproduce on Windows
@scorster we haven't been able to reproduce this yet, could you reproduce and share more details? (diagnostic files, if https://github.com/musescore/MuseScore/pull/25273 resolves it, anything else that might be relevent)
https://github.com/user-attachments/assets/2ad30800-1cda-4cfc-86c6-db20194f306d
(I'm using a screen keyboard as I only have the laptop keyboard right now Issues like https://github.com/musescore/MuseScore/issues/25373 are reproducible using the screen keyboard)
Cannot reproduce on macOS running Sequoia 15.0.
@scorster we haven't been able to reproduce this yet, could you reproduce and share more details? (diagnostic files, if #25273 resolves it, anything else that might be relevent.)*
video1380085280.mp4
(I'm using a screen keyboard as I only have the laptop keyboard right now Issues like #25373 are reproducible using the screen keyboard)
Are you using the virtual online keyboard available in Accessibility? (I don't see a way to show an extended keyboard from the Keyboard Viewer. Please advise.)
And I read the following on Stack Exchange, which might explain why we're getting different results:
"Clicking the NumPad numbers on this virtual keyboard sends the same key command as the top row of numbers."
All I can report is that with my official Apple Extended Keyboard the only functioning Numpad keys are: . augmentation dot + transpose up chromatically - transpose down chromatically / inserts acciciatura = enharmonic spelling
0 thru 9 on the Numpad have no effect.
MacOS 13.5.2, MuseScore 4.4.3 Apple Extended Keyboard
@scorster we're not sure why this is happening, but it does seem that resetting shortcuts to default solves the problem.
It would help our investigation if you could please add your diagnostic files to this issue.
Without this information, we will have to close the issue as we won't be able to further investigate it.
bkundawrote
... it does seem that resetting shortcuts to default solves the problem.
I see. Yes. Resetting the 0 .. 9 shortcuts it does fix the issue.
But this type of thing sure happens a lot. A QT issue?
@scorster Did you ever import shortcuts.xml from MS3 to MS4?
Did you ever import shortcuts.xml from MS3 to MS4?
Not that I recall. Is that something that MS4 suggests in a dialog or wizard? And the user accepts or declines?
If not, I doubt I'd have imported MS3 shortcuts.
Is that something that MS4 suggests in a dialog or wizard? And the user accepts or declines?
@scorster Nope.. You can do it manually in Preferences>Shortcuts>Import
I just noticed that yours shortcuts.xml file looks similar (after import) to MS3 shortcuts
MS3:
In default MS4 (or after Reset to default) 'set duration x' shortcut contains number and Num+number
@scorster But numpad keys work with imported MS3 shortcuts.xml and don't work with your file
As far as I know, the change to have both 5 and Num+5 listed as shortcuts for quarter note duration (and similar for the others) wasn't made until 4.0.1 - see https://github.com/musescore/MuseScore/pull/15824. So I think what probably happened here is, the people who experienced this problem had installed 4.0 - which didn't support numpad - and then customized some shortcuts before updating to 4.0.1 or any other post-4.0 release. The existence of the custom shortcut file then prevented the change from being picked up.
Now, why this would manifest as the numpad shortcuts working and then ceasing to work at 4.4.3 is another matter, but here I wonder if it's perhaps just slightly faulty memory. That is, perhaps they never actually worked. I notice the separate tab shortcuts are recorded correctly (with Num variants) in the given shortcuts.xml file. So maybe the actual story is, people with this file or one like it are finding numpad works for tab but not standard staves?
In any case, I would assume resetting those shortcuts should work.
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Reported here: https://musescore.org/en/node/371297#comment-1266682
Opening a new issue in favor of adding to this old one https://github.com/musescore/MuseScore/issues/12791#issuecomment-2458400738
Need to test: https://github.com/musescore/MuseScore/pull/25273
Supporting files, videos and screenshots
n/a
What is the latest version of MuseScore Studio where this issue is present?
4.4.3
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Mac OS
Additional context
No response
Checklist