[1.0] Chord navigation does not work on multistaff

• Mar 30, 2011 - 13:39
S4 - Minor

MuseScore 1.0 (fixed in trunk)

  1. Open this file
  2. Select the C chordname on second staff
  3. Press space

Actual result : The 2nd chordname of first staff is selected
Expected result : cursor should stay on 2nd staff.


The attachment above doesn't seem to work, but I can give very simply steps to reproduce:

1. create score with two staves
2. enter one chord per bar on bottom staff
3. select first rest of top staff, hit Ctrl-K, enter chord
4. hit space

I expect to be taken to the next measure of the top staff so I can enter a chord there, but am actually taken down to the staff below. The only way to enter chords on the top staff is to click each rest individually and hit Ctrl-K.

At this point, I'd like to reference an earlier feature request:


I had argued that we should have a way to move the chordname cursor beat by beat, rather than just note by note. This would make an unbelievably huge difference for jazz musicians. I had proposed we use the Tab key for this, because that key currently does nothing useful while in chord entry mode. Indeed, it's actually a royal pain if you should accidentally hit Tab instead of Space, as there is no way I can find to recover from this without leaving and re-entering chord entry mode.

So, *given* that the space bar logic is basically broken as is, and that Tab is basically worse than useless as is, I'd like to suggest that whenever someone gets around to addressing the space bar issue raised here, that they *also* consider whether something like my Tab suggestion could be implemented at the same time. I recall there were reservations expressed in a forum discussion about using that specific key, so make it another if you prefer - Ctrl-Space, maybe - and then perhaps disable Tab, or have it do something else useful (like, I don't know, invoke the parser to "spell check" the chord without moving on, or just make it a synonym for Space).

I don't know, it just seems like if you're mucking about with the chord name parser anyhow, this might be an opportunity to kill two birds with one stone.