musescore / musescore/MuseScore

Stave spacer up not working when upper instruments are hidden

Open
#26,865 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Create a score with multiple staves
  2. Select "Hide empty staves within systems"
  3. Find a system where the first visible staff is not actually the first of the piece, because one or more over it are empty and therefore hidden
  4. Add a stave spacer up
  5. Extending it up won't stop to the page or the page margin, and therefor won't move the system down as wanted
  • Please note that the problem doesn't appear in the opposite direction – with lower staves hidden and staff spacer dows, which correctly stop at page margins allowing the system to be moved up
Supporting files, videos and screenshots

Uncorrect behaviour with the hidden upper staves:
Image

Correct behaviour with hidden lower staves:
Image

What is the latest version of MuseScore Studio where this issue is present?

4.4 (also 4.5 beta)

Regression

No (same back to at least 3.6)

Operating system

Windows 11

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.