Lines placed above the top staff when single note selected.

• Nov 20, 2018 - 16:44
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

Create a score with more than one staff

On any staff besides the top one, select a single note
Double click a line that displays above the staff to apply it

Result: Line is displayed above the top staff
Expected: Line is displayed above the staff where the line is applied

Note 1: selecting an entire measure results in the line being displayed properly.
Note 2: saving, closing and opening the file corrects the display
Note 3: switching between continuous and page view has no effect
Note 4: Using ctrl+click to select the next note displays the line wrong
Note 5: selecting a group of notes using shift+click results in the line displayed correctly

Comments

• Dec 7, 2018 - 04:48

This one now wins for most-reported issue of the week :-)

Some clues: hairpins work by shortcut, drag * drop works, double-click on range selection works. Only double-click on single/list selection fail.

Reply

• Dec 7, 2018 - 09:08

Seems you won the early bird price, but not the most reported issue one, that was, I believe, the absence of the timewise delete menu in Beta

Reply

• Dec 8, 2018 - 19:01

OK, most-reported bug in functionality, then :-)

FWIW, I thought this would be a trivial fix in palette.cpp, but as far as I can tell, we are setting things up reaosnably, and the failure happens much later on, as we have trouble find the end element for the line and somehow this results in resetting the staff too. For anyone working wanting to work on this - check the application output in debugger and you'll see a complaint about endElement there. But the "track" and "track2" fields were correct as far as I traced up until then.

Reply

• Dec 13, 2018 - 19:10
Status fixed ⇒ active

Problem is still persistent in OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4482, revision: 2e2af50.

Note: I was using a custom workspace so I thought that might be a holdover since I put the new nightly on top of the old one so I switched to advanced with the same results.

Reply