Workspaces does not save palettes MuseScore 4.
I am trying to create a custom workspace in MuseScore 4 however changes to the palettes menu do not persist upon closing the application.
Changes I make to control visibility/layout work fine but any edits/changes I make to the palettes menu do not save upon closing the program. Upon relaunching, the palettes menu will revert to the default state, deleting any custom palettes and other element such as custom time signatures.
Is there a bug preventing the palette menu from being saved automatically, do I now need to manually save custom palettes, or is this functionality now separate from workspaces?
Comments
i’ve been having the same problem, and honestly it’s extremely frustrating. as for custom palettes, none of the methods i’ve tried seem to work (besides manually saving each and every one, but you’ll also have to manually load and reorder them in each time you reopen musescore), so i hope this gets resolved soon.
the changes i made to the layout don’t save either, so i wonder if i’m doing something wrong.
In reply to i’ve been having the same… by doodlerdoodlr
Some changes to existing palettes are not saved automatically (e.g. renaming) and you can't manually save them because Musescore defaults to a (WIndows 11) admin-only folder
In reply to Some changes to existing… by memeweaver
Yep, that's my experience too.
Any idea how to change the defaults?
In reply to Yep, that's my experience… by tejjy
Write Musescore code to make it work
In reply to Write Musescore code to make… by memeweaver
yeah, right.
I've thought about that many times - no evidence to date that the existing coding community is either welcoming or constructive in their engagement with new people, so not that keen. If you point me in the direction of the onboarding process/documentation, I'll consider it
In reply to yeah, right. I've thought… by tejjy
Unfortunately it's a bit of a closed club. The complete lack (or confusion of multiple conflicting) onboarding documentation is a deterrence. They'd rather harangue every person individually for not knowing all the arcane secrets or rules of the day for engagement, than actually make it a welcoming professional development environment.
In reply to Unfortunately it's a bit of… by memeweaver
I thought C++ was all the deterrence anyone needs :-)
In reply to yeah, right. I've thought… by tejjy
Actually, there is a thriving community of developers with new folks joining all the time! To learn how to get involved, see the Contribute / Development menu above.
As for whatever issue you are seeing with workspaces, feel free to describe in more detail. Workspaces are saved automatically on program exit or workspace change, but you do need to be careful not to have multiple instances overwriting each others’ changes.
I'm not having this problem, but one thing I wonder - do you perhaps have multiple scores open and making different changes in different windows that are clobbering each other? I've made that mistake.
In reply to I;m not having this problem,… by Marc Sabatella
Ah yes I think that is what's causing the problem. It seems multiple windows do cause issues with saving workspaces as I am no longer having this problem now I am ensuring to only open one file at a time. Thanks for your help Marc.
In reply to Ah yes I think that is what… by Whitefang165
Even with only one window open my changes to the custom palettes don't seem to save across multiple files... I have multiple versions of my custom palette now, depending on the file I open
In reply to Even with only one window… by casvlaco
See also https://github.com/musescore/MuseScore/issues/13837 and perhaps join the discussion there.
In reply to See also https://github.com… by SteveBlower
That discussion is not helpful.
On my fourth attempt, the custom palette I had created re-appeared after shutting down and re-starting. That's good.......