musescore / musescore/MuseScore
Configure the System markings position in parts
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Add, in the layout panel for parts, the possibility to configure the position of System markings, like in the main score.
Problem to be solved
Today, in parts, contrary to in the main score, it is not possible to specify which System markings should appear where.
They are always placed on the top of the score, even if in the main score they are placed at the bottom.
A workaround, in parts, is to press "X" on all the system markings. But:
1/ this is time consuming, while it could be automated
2/ this does not work when the part contains more than one staff
3/ the format changes you do on these system markings on the main score are not push to the parts(*)
Examples:
Main score layout:
Main score result:
Result in the Piano part:
Result in the Sax part (with an additional part for the drum beats):
###
Part Configuration
Main score system markings
Not shown in layout part
Adding a system marking layout element:
Not possible. The option is grayed.
Prior art
No response
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the parts layout panel and the existing main-score System markings configuration. Trace how marking positions are stored and applied when generating parts, including parts with more than one staff. Done means parts can configure which System markings appear at the top or bottom and preserve the relevant main-score formatting.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100