I'm glad I didn't install the Beta and lose all of my shortcuts. Does this mean the issue needs to be closed, or is the an issue with the way the Beta was created.
Installing the beta won't lose your development builds' shortcuts.
This problem is for the Beta and the Beta only. Where and why is still to be determined, could be released to packaging, but definitely is something that needs fixing.
My impression you wouldn't "lose" your shortcuts; they should be maintained separately from master builds anyhow. Meaning. your master shortcuts are still your master shortcuts, stored in MuseScore3Development folders, whereas the beta would keep everything in MuseScore3. But you could presumably copy over your shortcuts once this issue is figured out. That's my assumption anyhow.
EDIT: I tested, and this is true. Copying shortcuts.xml from your MuseScore3Development folder to MuseScore3 definitely works to retain custom shortcuts, even though they don't display in the dialog. As for where to find these folders, that's OS-specific. On Windows, C:\Users\Marc\AppData\Local\MuseScore\MuseScore3 (substitute your own user name for Marc)
If installing the beta puts it in a new folder, then it should not be surprising that your nightly shortcuts are not there, they're in the folder where you left them for your nightlies. You should just be able to copy the shortcut list to the new directory. Or am I missing something?
Yes, you are mississing something: the shortcuts dialog on the Beta is just empty. I don't expect the nightly shortcuts there at all, but I expect the default shortcuts, for me to change.
The file shortcuts.xml is actually there, and in effect, it ist just not shown in the dialog, so can't get changed (not via the UI at least)
Culprit is 72d64c91, by yours truely... OK, so I'll be wearing a brown paperbag over my head for the rest of the day then ;-)
Intention was to hide the save-online shortcut in unstable builds unless the -e option is used, apparently I screwed up the logic.
Comments
not an issue with a self-built version from the master branch
Yep, confirmed with the beta, but not with the last available nightly (revision: af128b5)
In reply to Yep, confirmed with the beta… by kuwitt
I'm glad I didn't install the Beta and lose all of my shortcuts. Does this mean the issue needs to be closed, or is the an issue with the way the Beta was created.
Installing the beta won't lose your development builds' shortcuts.
This problem is for the Beta and the Beta only. Where and why is still to be determined, could be released to packaging, but definitely is something that needs fixing.
My impression you wouldn't "lose" your shortcuts; they should be maintained separately from master builds anyhow. Meaning. your master shortcuts are still your master shortcuts, stored in MuseScore3Development folders, whereas the beta would keep everything in MuseScore3. But you could presumably copy over your shortcuts once this issue is figured out. That's my assumption anyhow.
EDIT: I tested, and this is true. Copying shortcuts.xml from your MuseScore3Development folder to MuseScore3 definitely works to retain custom shortcuts, even though they don't display in the dialog. As for where to find these folders, that's OS-specific. On Windows, C:\Users\Marc\AppData\Local\MuseScore\MuseScore3 (substitute your own user name for Marc)
In reply to My impression you wouldn't … by Marc Sabatella
If installing the beta puts it in a new folder, then it should not be surprising that your nightly shortcuts are not there, they're in the folder where you left them for your nightlies. You should just be able to copy the shortcut list to the new directory. Or am I missing something?
Yes, you are mississing something: the shortcuts dialog on the Beta is just empty. I don't expect the nightly shortcuts there at all, but I expect the default shortcuts, for me to change.
The file
shortcuts.xmlis actually there, and in effect, it ist just not shown in the dialog, so can't get changed (not via the UI at least)https://github.com/musescore/MuseScore/pull/4256
which reveals an interesting workaround: use the -e option (used to enable experimental features)
Culprit is 72d64c91, by yours truely... OK, so I'll be wearing a brown paperbag over my head for the rest of the day then ;-)
Intention was to hide the save-online shortcut in unstable builds unless the -e option is used, apparently I screwed up the logic.
Fixed in branch master, commit 61174478e1
Fix #278970 Preferences/Shortcuts not shown (and so not changable)
Fixed in branch master, commit 81b699ca13
Merge pull request #4256 from Rockettwo/fix278970_shortcutsNotShown
Fix #278970 for Beta: Preferences/Shortcuts not shown (and so not changable)
Fixed in branch 3.0beta1, commit 21a648e6de
Merge pull request #4256 from Rockettwo/fix278970_shortcutsNotShown
Fix #278970 for Beta: Preferences/Shortcuts not shown (and so not changable)
Automatically closed -- issue fixed for 2 weeks with no activity.