musescore / musescore/MuseScore
Find command should allow you to specify a particular staff
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
If you use Ctrl+F to go to a particular measure, you are always positioned on the top staff. This is an accessibility issue mentioned by several blind users, since in a large ensemble score, it can take many keystrokes to get down the staff you want.
The suggestions here is twofold:
- If the current selection at the time before executing the Find command is a single element or a range on a single staff, then the Find command should select the target measure on that staff instead of the top staff
- there should be a syntax to specify a particular staff directly in the find command, like "4:20" to select measure 4, staff 20.
Problem to be solved
The Find command makes it easy to navigate to a specific measure, but there is no way to target a specific staff. This would also be useful when trying to fix corruption issues, since that info is presented as measure and staff number.
Prior art
I'm not aware of what facilities other programs provide.
Additional context
The measure:staff syntax would still be useful without the change to the default behavior, should it be decided not to change that.
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 by locating the Find command invoked by Ctrl+F and inspect how it chooses the target measure and staff. Check the current selection handling and find-entry parsing, then verify that both the single-staff selection behavior and the proposed measure:staff syntax select the intended target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100