search

musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.18k stars 2.64k forks source link

Palettes expanded/collapsed state not persisted #17064

Open j-raybaudserda opened 1 year ago

j-raybaudserda commented 1 year ago

Issue type

UI bug

Bug description

The state of the palettes (whether they are expanded or collapsed) in the UI does not persist when Musescore is closed, meaning that every time the application is launched, each palette needed to work (or all of them if using the Expand all Palettes option of the Palettes pane) needs to be manually expanded, which is time consuming and frustrating.

Back in Musescore 3.X, it used to be that the state of the palettes would persist between sessions, meaning that the program would reopen with the palettes in the state in which they were left when closed. Either this is a bug in Musescore 4.X, which should be corrected, or this is a wanted behavior, in which case a good middle ground could be to implement a "Palette persistance" option in the parameters to let users choose wether or not they want their palettes state to persist between sessions.

Steps to reproduce

  1. Open Musescore and create a new score (or open an existing one)
  2. In the Palettes pane options, click on Expand all Palettes
  3. Close Musescore
  4. Reopen Musescore and reopen the previous score
  5. All the palettes are once again collapsed

Screenshots/Screen recordings

No response

MuseScore Version

4.0.2.230651546

Regression

Yes, this used to work in Musescore 3.x and now is broken

Operating system

macOS 10.15.7

Additional context

OS: macOS 10.15 Arch.: x86_64 MuseScore version (64-bit): 4.0.2-230651546 revision: github-musescore-musescore-dbe7c6d

bkunda commented 1 year ago

Are we talking here about whether one or more palettes remain open or not between sessions? If this is the case, then this information should be stored to the file, because it wouldn’t always make sense for the same palettes to remain open between different projects.

j-raybaudserda commented 1 year ago

Precisely, it used to be that the palettes that were opened during a session remained open between the sessions if not closed manually (and the closed ones stayed closed as well). Given the fact that the list of palettes does not change between sessions (except if modified manually, which makes it non project dependant), it seemed fitting to me to have a global option to control this behaviour.

cbjeukendrup commented 1 year ago

If this is the case, then this information should be stored to the file, because it wouldn’t always make sense for the same palettes to remain open between different projects.

I disagree. Palette state is a property of the user's workspace, not of a score file. Also, different users have different palettes configurations, so the expanded/collapsed state would not be compatible. So, palette state should be stored on the user's computer, together with the palettes themselves.

FranckDhersin commented 1 year ago

Hello, I have reported the bug #19450. I agree with you @cbjeukendrup but this information (the Palettes Display Status) should be stored somewhere in the personal computer (maybe in a file visited whenever an instance of MS is opened or closed).

I work on a lot of scores and each time I open Musescore, it is convenient to always have the same Palettes-Submenus opened. So that I don't have to open it each time I want a tempo or an articulation or whatelse.