musescore / musescore/MuseScore

Sizing issues when using vertical frames and multi-measure rests

Open
#23,883 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

When resizing vertical frames for spacing staves, multi-measure rest widths on adjacent staves will lengthen uncontrollably, effecting the note spacing, bars per staff, and overall readability of the score. There is no method for manually resizing the width of multi-measure rests. This only happens in some parts/scores, not at all times.

STEP BY STEP

  1. Open "Hot In Herre" (attached below)
  2. Open "Alto Saxophone"
  3. On a staff which has a multi-measure rest, add a vertical frame. (Palettes > Layout > Insert Vertical Frame)
  4. Resize the vertical frame with the mouse our arrow keys, and observe the multi-measure rests on neighbouring staves widening.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/d7f69934-e131-4f60-99c5-35bfdd6ec212

Hot In Herre.mscz.zip

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

OS: macOS 14.4, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630832, revision: github-musescore-musescore-22b46f2

Regression

I was unable to check

Operating system

macOS 14.4.1

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.