Rearranging palette symbol order

• Jun 10, 2024 - 21:16

Unless I'm a dummy (and it's quite likely I am), I don't see a way in MS4 to do the following with the Palette symbols. I believe some of these actions were available in MS3, although not in a consistent way from score to score (its memory wasn’t so good).

  1. Rearrange the palette symbols in a particular way so that they remain in those positions every time the same score or a different score is opened.

  2. Remember from score to score what symbols have been deleted (moved to the Move folder).

  3. Adjust the symbol size for EACH symbol and remember it from score to score.


Comments

Number 1 is easy. Just drag and drop the palettes to the order you want. Exit the score (if you have multiple scores open, exit all OTHER scores first, then the one you were in when you made the change last!) and relaunch it. MuS will now remember the order you set in all future scores it opens.

I don't understand your number 2.

Number 3 is (mostly!) a style setting. Format / Style and make your settings. Then save a style file per the instructions at https://musescore.org/en/handbook/4/templates-and-styles.

I've never even tried this, but I've read posts that some items are not saved in a style file. I don't know the details, sorry.

In reply to by TheHutch

Thank you for your response, but none of your suggestions work for me in the latest version of Musescore 4 that I’m using (V 4.3.1.241490900).

To clarify, all custom changes made to the palettes by the user are not retained. Once you make the changes, exit the score where you made the changes, or exit the program, it's groundhog day all over again the next time you open MS4. This needs to be fixed in a future version.

In reply to by artoffugue333

artoffugue333 wrote > To clarify, [In (V 4.3.1.241490900)] all custom changes made to the palettes by the user are not retained. Once you make the changes, exit the score where you made the changes [are lost.]

I think this is an insidious side effect of the multi-App-instance scenario that MS4 foisted on us.

For instance, if you've opened multiple documents (hence multiple instances) you may get a different palette preference result depending on which instance you close first ... or last. (I don't know for sure, as I can't tell here because here on MacOS, because MuseScore 4.3.1 crashes on Quit, which likely interrupts the palette preference save.)

You could experiment by opening a single document, then update a pallet and Quit. If MuseScore manages to quit without crashing your altered pallet should open in any new instance of the app.

That said, your could resort to an awkward workaround: Save your palette as a custom palette and reopen it whenever you need. Or until it "sticks."

scorster

In reply to by artoffugue333

If you open MuseScore - only once, make the changes and close MS, the changes are retained. (you don't even have to open a score)
Those changes are not saved in a score, but in a 'workspace' . Config file in MS config directory MuseScore/MuseScore4/workspaces/Default.mws/palettes (in Linux: ~/.local/share/MuseScore/MuseScore4/workspaces/Default.mws/palettes )
You can have a different palettes config if you make a new workspace.
Since those are not saved in the score, "remember from score to score" cannot work.

In reply to by artoffugue333

Actually, you don't have to do that. It's just good practice to create a new workspace when doing extensive customizations, so you can easily return to the default configuration. But it totally works to do your customizations to the default workspace. You just have to be careful not to have two different sets of customizations in two different open windows as only one set can "win" the next time MuseScore Studio is opened.

In reply to by Marc Sabatella

Thanks for you comment Marc: You have to be careful not to have two different sets of [palette] customizations in two different open windows as only one set can "win" the next time MuseScore Studio is opened.

Do you know if this issue is mentioned anywhere in the palette documentation?

Do you still have an unanswered question? Please log in first to post your question.