musescore / musescore/MuseScore

Hide bar numbers/measure numbers at rehearsal marks

Open
#20,046 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

An option to hide bar numbers at rehearsal marks would be very helpful, such as a "Hide at rehearsal marks" checkbox in Style > Bar Numbers.

Problem to be solved

Currently, the bar numbers set up by MuseScore appear whether or not there's a rehearsal mark at the same position; this often causes collisions and looks especially weird if the rehearsal marks use bar numbers.

There are a couple of existing manual workarounds, including hiding the offending number directly, using bar properties to set the number to always hide, or a plugin that can be run periodically, but this either means extra steps while writing the score (especially if any rehearsal marks move), or another step on a manual checklist at the end before publication.

Having an option for this to be automatic in software would let the user concentrate on the music.

Prior art

Sibelius has had this for some years in its engraving rules.

Additional context

Migrated from the old issue tracker at https://musescore.org/en/node/112721.

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.

Research direction

Start at the Style > Bar Numbers settings described in the issue and trace how bar numbers and rehearsal marks are positioned. Confirm the existing manual hide behavior and determine where an automatic “Hide at rehearsal marks” option belongs. Done means the option prevents colliding bar numbers while preserving the current behavior when it is disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
design, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.