musescore / musescore/MuseScore

Hiding top note of a chord on extra staff line causes every extra staff line to be hidden

Open
#14,994 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug
See screenshot. When you hide a note of chord the "extra staff lines" will get invisible, causing the visible notes to "fly" above the staff.

To Reproduce
Steps to reproduce the behavior:

  1. Place a chord with notes above the usual staff.
  2. Hide a note thats ON a extra staff line.
  3. See the bug.

Expected behavior
Only the extra lines which are not needed to display the whole visible chord should be invisible.

Screenshots
Top note hidden:

Screenshot 2022-12-06 181121

Additional Context
Doing this is needed for something like this: https://musescore.org/de/node/277181 .
This is also a problem in MS3, so I think MS4 should make it better. Also the stem, which connects the top note with the rest of the chord should get invisible, so theres no rest of a stem on the final sheet.
Workaround to this bug was to just place the note in the second voice and hide it. However I think fixing this will improve user experience.

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.

Research direction

Start by reproducing the issue in MuseScore using the three steps described, then trace how hiding the top chord note determines extra staff-line visibility and the remaining stem rendering. Done means only unnecessary extra staff lines are hidden, visible notes remain aligned with the staff, and the hidden note's connecting stem is not left visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.