musescore / musescore/MuseScore

Vertical frame height does not sync between score and parts

Open
#30,090 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

To reproduce:

  1. Start a new project with multiple instruments.
  2. Add a vertical frame above the first system.
  3. Change its height.
  4. Open a part.

Actual behavior:
The vertical frame still has its default height.

Expected behaviour:
The frame should have the height set in the score.

Supporting files, videos and screenshots
Image Image
What is the latest version of MuseScore Studio where this issue is present?

OS: macOS Monterey (12.7.6), Arch.: arm64, MuseScore Studio version (64-bit): 4.6.0-252660405, revision: github-musescore-musescore-88ab447

Regression

I was unable to check

Operating system

macOS 12.7.6

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.

Research direction

No source files, tests, or entry points are named. Start by reproducing the issue with a project containing multiple instruments, then compare the vertical frame height in the score and an opened part. Done means a changed frame height in the score is reflected in the corresponding part.

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.