Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
4 tasks done
Dima-S-Jr opened this issue Jan 25, 2025 · 0 comments
Open
4 tasks done

Comments

@Dima-S-Jr
Copy link

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

Video_250126005254.mp4

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants