musescore / musescore/MuseScore

Individually styled measure numbers lose styling on toggling MM rests.

Open
#34,070 1 comment 0 reactions 1 assignee View on GitHub

@davidstephengrant is already working on this.

Since Jul 7, 2026.

engraving P3 regression MS4 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 new score
  2. Select a visible measure number and change its style in the Properties panel
  3. Toggle multi measure rests on.
  4. Undo. (Or toggle MM rests back off).

Expected behaviour:
The measure number retains its custom styling.

Current behaviour:
The measure number reverts back to default.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/5b508a84-bf27-4c13-8a41-102a0124f0ea

In which versions of MuseScore Studio is this issue present?

4.6.5 – main latest nightly

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows, macOS

Additional context

Reported and discussed in https://musescore.org/en/node/394552

As the screen capture shows, excluding an earlier measure from the measure count does not make the styling revert back to default, even though the actual number updates. Changing the time signature or the measure number frequency in Format > Style does make it revert.

The latest version this worked in was 4.5.2

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.