musescore / musescore/MuseScore

Shift + [chord key] for the trill cue note results in endless ledger lines

Open
#26,239 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

Imagine that a user wants to add a chord note to a trill cue note. What is he doing:

  1. Enter a chord of two (or more) notes
  2. Add a trill line to the entered chord
  3. Enable the cue note visibility in the trill Properties
  4. Click on the displayed trill cue note
  5. Press the key combination Shift + [chord key from A to G]

The trill cue note will move up an uncountable number of ledger lines. Obviously, this should not be the case.

Expected behaviour

In general, the trill cue note should have been initially displayed as a chord, and then the user would not have to resort to this kind of manipulation. As a result, there is a contradiction between what is written and what sounding:

Image

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/4bb41ea1-b88a-4abe-8621-b41f966090fd

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

4.5.0 250250300, revision: 3255273

Regression

No.

Operating system

Windows 11

Additional context

I think it would be great if the solution to this issue was solution #18931. Although the user should be able to manage this.

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.