musescore / musescore/MuseScore

Allow for customization of notation elements "stacking order" in parts

Open
#26,096 2 comments 1 reaction 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

Bring back stacking order for text styles and notation markings in parts

Problem to be solved

One of the notation conventions in the gig I'm doing encourages measuring numbers in the center of each bar. However, using MuseScore makes this quite difficult. Even if I use the offset tool for every single element in only the parts, I then have to adjust the auto-place in each part, which becomes very laborious with my time constraints.

A stacking order would allow me to keep measuring numbers at the time no matter what, notwithstanding autoplace or anything like that.

I've attached an example of what I would like MuseScore to optimize:
Screenshot 2025-01-14 at 18 09 25

Prior art

They solve it by simply making it an option to put measure numbers at the very center at the bottom edge of the instrument stave

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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

The issue names parts, text styles, notation markings, measure numbers, autoplace, and the offset tool, but no files, tests, or entry points. Start by locating the parts layout and autoplace implementation, then determine how stacking order should interact with those controls. Done means users can customize stacking order for notation elements in parts without manually adjusting each element.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.