musescore / musescore/MuseScore

Properties major quality of life changes necessary

Open
#16,524 1 comment 0 reactions 1 assignee View on GitHub

@Tantacrul is already working on this.

Since Feb 24, 2023.

P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

There are a plethora of changes that could be done to the Properties panel that would improve quality of life.

Overall, making the entire UI for Properties not as large. There's no reason why every button and setting should be taking up that much individual space, and no reason why each button should have so much dead space within it. It feels bulky/clunky and is actually more difficult to navigate bother vertically and horizontally.

Notehead Type should be collapsible, a majority of scoring situations will not use this and it is taking up unnecessary space by being unable to collapse it.

Playback button in Properties is especially egregious. Why even show all of these greyed-out options if they aren't relevant to the situation at hand? If I'm trying to adjust the velocity on a note, I don't need to see 5 greyed-out options that have no relevance, as you can't even interact with them unless you are specifically selecting the objects that are named under the playback button. Instead of clicking on an arpeggio and immediately seeing "Spread Delay", instead I have to select the arpeggio and select Playback, all while having 5 greyed-out options drown out the rest of the space. Seriously backwards and redundant, massive design issue that needs to be reworked. Also, clicking the playback/appearance button while scrolled lower in the Properties panel obscures the view of "Visible, Auto-place, cue size, play" buttons if you scroll back up after.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.