musescore / musescore/MuseScore

Newly added note-anchored line has zero length (sometimes)

Open
#28,168 1 comment 1 reaction 1 assignee View on GitHub

@miiizen is already working on this.

Since May 28, 2025.

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
  1. Create a new score with piano.
  2. Add notes as seen in the screenshot below.
  3. Select notes 1S & 1E, and click Add > Lines > Note-anchored line.
  4. Repeat step 3 for notes 2S & 2E, 3S & 3E, and 4S & 4E.

Current behavior (4.5.2): A line appear between 1S & 1E; a very short line appears between 2S & 2E; no (visible) lines appear between 3S & 3E, and 4S & 4E. Upon closer inspection, one finds that lines are actually added to the score for 3S & 3E, and 4S & 4E, but they have zero length. Thus, they cannot be selected with the mouse cursor.

Workaround: Select the bar to which the (zero-length) note-anchored line has been added, then go to the "Properties" panel, and click on Notation > Note-anchored line. Then, in the "Text" tab, add a "Beginning text". This forces the note-anchored line to be visible, and it can then be selected with the mouse cursor. After moving the endpoints, the "Beginning text" can be removed and the line remains visible.

Expected behavior: Lines connecting the noteheads should be added for all pairs 1S & 1E, 2S & 2E, 3S & 3E, and 4S & 4E.

Supporting files, videos and screenshots

Image

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

4.5.2.251141402
I have also checked the nightly build (May 27, 2025), and the issue is still present

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.