musescore / musescore/MuseScore

Cannot adjust height of cross-bar beam under some circumstances

Open
#28,563 3 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

If a cross-bar beam is added between the first two bars of a system which is not the first system in the score, then the height of the beam cannot be edited. This occurs no matter whether the numerical beam height is edited in the 'Properties' tab, or the beam is dragged in the score.

To reproduce:

  1. Create a new score with piano
  2. Add two notes as seen in the screenshot below
  3. Drag the beam up or down. The beam will move on the very first mouse-move event, and will then freeze. The amount of movement depends on how much the mouse is moved in this single event.

Workaround:
Type out the two measures with the cross-bar beam somewhere else on the score, adjust the beam height, and then Cut+Paste to the correct location.

Supporting files, videos and screenshots

Image

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

4.5.2 and nightly build

Regression

No

Operating system

Windows 10

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.