After you change the pitch of a note that's tied, both tied notes end up selected.
Reported version
3.0
Type
Functional
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
1) Write any chord in which some or all of the notes are tied to notes on a different beat.
2) Scroll among the notes of this chord with your custom keyboard shortcut. It works fine.
3) Once you reach any note that's tied, change its pitch either up or down.
4) The other tied note moves along with the one you moved manually, but afterwards both notes end up selected, which means you can't keep scrolling with that keyboard shortcut.
This goes against the main purpose of that command.
Fix version
3.1.0
Comments
From my perspective, having both notes selected would not be a problem if the navigation keys all worked even with multiple notes selected. Right now apparently most commands work but Alt+Up/Down does not, nor does Alt+Left/Right.
The code that selects both notes was added in 699b9af, presumably for the sake of the piano roll. When blackears redesigned the piano roll editor (63d2db7), he added a way to bypass this code for piano roll events, thus defeating the original purpose, but leaving us with the side effects. This code should probably be removed altogether. See https://github.com/musescore/MuseScore/pull/4979.
Fixed in branch master, commit 58e59f9477
fix #288528: After you change the pitch of a note that's tied, both tied notes end up selected.
Fixed in branch master, commit d103b8f417
_Merge pull request #4979 from mattmcclinch/288528-change-pitch
fix #288528: After you change the pitch of a note that's tied, both tied notes end up selected._
In reply to Git webhook message by Git Message
Great!
Automatically closed -- issue fixed for 2 weeks with no activity.