musescore / musescore/MuseScore

Trill lines applied from palettes have no line when applied via list selection

Open
#33,982 4 comments 0 reactions 2 assignees View on GitHub

@mathesoncalum is already working on this.

Since Jul 1, 2026.

P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Description edited by @mathesoncalum - this issue initially outlined two problems; one severe regression relating to a "sticky selection" of trills (now resolved here) and the other relating to the length of trills applied from palettes (outlined below).


Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Add a note in two different staves
  2. Select the two notes
  3. Click the Trill line ornament from the palette.

Expected: the notes have a tr over them with a wiggly line (as is the case for a range selection).
Actual behaviour: the notes have a tr, but no wiggly line.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/913462b2-5867-41ec-9893-4efc3b7eea7d

In which versions of MuseScore Studio is this issue present?

OS: macOS Ventura (13.6.3), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.3-260608135, revision: github-musescore-musescore-cf9860c

Regression

I was unable to check

Operating system

macOS

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.