musescore / musescore/MuseScore
Custom palette doesn't save in some cases
Open
Nobody has claimed this yet.
P2
palettes
regression MS3
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Palette issue
Steps to reproduce
For now, I found two cases when custom palette doesn't save and doesn't appear on the app next start
- When custom palette is created in a first instance of MU, then you start and close a second instance of MU, and then you close the first instance
https://github.com/musescore/MuseScore/assets/90187801/212db9c5-c449-43e5-9d95-a1a840f7990b
- When MU crashes on quit (or during session)
https://github.com/musescore/MuseScore/assets/90187801/7671b31c-4d3a-46fd-9b14-f659f347debb
MuseScore Version
4.1 master (dev)
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Also broken in 4.0.0, 4.0.2
Operating system
Windows10
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.