Note input cursor resets to beginning of bar when clicking to enter notes on tab staff

• Aug 18, 2014 - 15:07
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

Ubuntu Studio 14.04, GIT commit: 975f4df

1) new score for guitar tab
2) first measure, note entry
3) click top string to enter a note (fret 0)
4) click to the right of that note to enter a second note

Result: note input cursor backs up to beginning of bar

It remains there if you enter more notes.

I discovered this while checking to see if #25867: Standard staff linked to TAB staff shows wrong notes on some combination of mouse+kbd note entering. was still active (it is). Wondering if these two issues will turn out to be related.

Not sure if this behavior has been around a while or if it broke as a result of other recent note input cursor changes.

Comments

• Aug 18, 2014 - 16:15

I had never noticed this behavior, and I used Tabs almost every day.

After verification, I can say that this is very new, less than a day (or few hours !)

-The issue is active since the Nigthly, August 18 (24700da), and so with followings.

- The immediate previous Nigthtly, August 17 ​​(fe89f44) works well, and others previous.

Reply

• Aug 18, 2014 - 17:27

The problem appears to be with a fix made for #29756: Selection of tablature includes previous bar - specifically, the change within ScoreView::posChanged() to call moveCursor(tick) rather than moveCursor(). moveCursor(tick) is designed to be called during playback, and in particular, only after doLayout(). moveCursor(tick) depends on the canvas position of the segments in the measure, and this has not been calculated yet.

Without fully understanding the issue that led to this change, I suspect that a "better" fix might have been to make sure things were set up properly to allow the tick-less moveCursor() to work as expected. I'm sure there is some reason that is harder than it sounds, though...

Reply