Note Entry - "Guessing" when going into note-entry/next-prev element from tuple text

• Jun 16, 2020 - 02:59
Reported version
S5 - Suggestion
needs info

1) Select a tuple bracket
2) Utilize [go to next/prev element]
MS "Guesses" and goes back to the system's barline before the clef/keysig if any. This isn't too bad most of the time since it's rare to issue next/prev element when selecting a tuple, but it does happen at times. Beats crashing the program like in the past

Also, Note-entry works correctly so long as only one tuple is selected. If multiple tuples are selected when the user presses N, note-entry begins at the beginning of the entire score. If the user selects multiple notes (ctrl+click for example), then presses "n", note entry begins at the first element timeslot of that list of notes.

The suggestion is to have this be consistent and have the same behavior apply with the tuple bracket also rather than starting at the beginning of the score. That is, the first tuple in the selection of tuples: the first chord/rest element within it ought to be selected and used for note-entry position.

Of course the user can press escape first, and then note-entry doesn't do anything that seems out of the ordinary. One problem here though is that when making invisible a group of tuple-brackets (for example, select all similar: same system and then press 'v'), the user doesn't have visual feedback as to when they are selected or not selected, so visually there's no distinction between before pressing escape and after pressing escape in that instance. That means that when going into note-entry directly from that position, there's no visual cue as to whether the user will get to the beginning of the score or to the beginning of the selection. And the user can't use "next element/previous element" command while having this group selection. Either press "escape" then hope for the best with [next/previous element] or [note entry] (and this is actually pretty decent, as it works well after pressing escape) , or get your hands back on the mouse. Not that big of a deal, but in the long run this is a corner case that should be made a little more consistent as related to not needing escape with note selection. Certainly not time-pressing.