musescore / musescore/MuseScore

Element is not selected by 'Select All' if display measure is different than attached measure

Open
#30,620 1 comment 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Oct 21, 2025.

community needs review plugins 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

DESCRIPTION OF CURRENT BEHAVIOUR: I've written a plugin that attaches text boxes to a score at particular ticks. If there is no note at that tick, however, MuseScore states in the info bar at the bottom that the 'display measure' is not the same as the actual tick measure. That's fine, but I've found that these objects are not able to be selected when you choose 'Select All'. (See test score below).

I'm not sure if this is a regression, but I don't remember seeing this happen before.

EXPECTED BEHAVIOUR: All objects should be selected by Select All, regardless of what the display measure is.

Test score.mscz.zip

Supporting files, videos and screenshots

In this screenshot, I have chosen Select All. Note that the comment box is not selected.

Image
In which versions of MuseScore Studio is this issue present?

4.6.2

Regression

I was unable to check

Operating system

macOS 15.7.1

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.