musescore / musescore/MuseScore
Exclude hidden staves from new additions to vertical range selections
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
When making a range selection across multiple staves separated by a hidden stave then entering a new addition to the score, such as dynamics, the addition shouldn't go onto the hidden stave.
Problem to be solved
For SSAATTBB vocal scores I sometimes have SATB sections and to keep them named correctly I actually have staves for S1/S/S2/A1/A/A2/T1/T/T2/B1/B/B2 and hide empty staves turned on. When adding dynamics (either text or hairpins) to this number of scores, creating a discontinuous selection takes ages, so I'd prefer to just create a range selection and add the dynamics to all staves. This works fine if there are no hidden staves - the dynamics are added and all is well, but when there are hidden staves, the dynamics get added to not just the visible staves, but also the hidden ones, causing them to become visible. I then have to delete all the wrong dynamics, which takes just as long as selecting the eight original ones!
The above scenario is my most common example, but there are many other situations where I have hidden staves which shouldn't receive the same additions as the visible ones.
Prior art
No response
Additional context
No response
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
No file or test is named. Reproduce the issue in MuseScore with a range selection spanning hidden staves, then trace the path used when adding dynamics or hairpins. Done means additions affect the selected visible staves without making hidden staves visible or adding content to them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100