musescore / musescore/MuseScore
Inconsistent input staff logic after select-deselecting measure or note
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Bug description
If I select and deselect a measure in a certain staff, the input cursor (after pressing N) won't move to that staff;
But if it was a note or a rest, the input target cursor will move.
I expect the cursor always following most recent selection, regardless of measure or note.
Steps to reproduce
This is input cursor not following a 'selected then deselected' measure:
- Make sure input cursor is on violin staff after pressing N
- select piano treble staff, press N without deselecting it, input cursor moves to this staff (expected);
- move input cursor back to violin staff
- select piano treble staff then deselect it, then press N, input cursor stays on violin staff (not expected)
and this is input cursor following a 'selected then deselected' note:
The step is the same as above, except it was a rest rather than a measure being selected; but in step 4 of this case, input cursor will move to the selected-deselected staff.
Screenshots/Screen recordings
No response
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf
Regression
No.
Operating system
Windows 11 22H2
Additional context
- It behaves the same in 3.x
- I'm bothered by this because I use select-deselecting a measure to listen to the whole system
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.
Assessment
This issue has not been assessed yet.