musescore / musescore/MuseScore
In note input mode, after inputting a note, holding shift should temporarily move the input cursor back
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
Holding shift after entering a note already lets you add notes to create a chord at the last-entered note, but while doing so, the note entry cursor remains on the next input location.
It would be nice if there was visual feedback that moved the cursor to where a note will be input while shift is being held. Releasing shift would move the cursor back where it started. So holding/releasing/holding/releasing would look like this:
Problem to be solved
Make it more obvious what holding shift does when in note input mode.
Additional context
Note that shift would only move the cursor back if you just entered a note. If you've moved the cursor with the arrow key, the cursor location and the entry point of Shift + [A–G] is the same, because of where the selected note is, so shift wouldn't do anything visually in this case.
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
Reproduce note input mode and the existing Shift behavior using the issue description and attached examples. Locate the note-entry and cursor-handling entry points, then trace how a just-entered note differs from a cursor moved with an arrow key. Done means the cursor visibly indicates the Shift note position while held and returns to its prior position when released.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100