Accidentals added to trill lines not displayed until redraw

• Sep 2, 2020 - 16:50
Reported version
S4 - Minor

Add a trill from the lines palette to a note.
Select the trill line and click an accidental in the palette

Result seemingly nothing happens except the score display jumps to the beginning of the score see #309970: Adding accidental to trill line causes display to jump to start of score for this issue

Force a redraw (I usually select a rest and press up arrow followed by down arrow

Result the accidental is now visible


Status active needs info

I'm not able to reproduce this in a score I created from scratch. I rather doubt something like this could be connected to a specific score, but to be sure - could you attach one that demonstrates the problem?

I'm guessing any differences would have more to do with view menu & preference settings (e.g., some combination of settings involving page vs continuous view, zoom setting, draw antialiased, show invisible, etc). Slight chance, I guess, that it relates to the music font.

Status needs info active

Never mind, I can reproduce, the key seems to be the detail from the linked issue, the trill has not not be on page one, or otherwise such that a reposition of the score view moves it out of view.

I'm not sure I ever tried this on page one of a score but it always happens to me. I guess it's good I decided to add the screen jump also and link the two issues. They may be one fix but to me they are different enough I decided they should be split. If you fix this and decide they should be merged then by all means mark one as a duplicate with an explanation.

I think there is a very good chance the underlying cause of both will turn out to be the same, something having to do with the accidental not being added to the page properly (note to whoever works on this, whether future me or someone else: missing call to rebuild bsptree?) which could cause both the bad repositioning and the lack of drawing. But definitely, we will need to check both symptoms, and it's possible separate fixes will be needed, so just as well the issues are separate.

I will guess the issue showed up around 3.3 (?) when there was a pretty significant change to the code responsible for repositioning the score.

I think the issue existed in 3.2.3 since I skipped the 3.3 releases I'm not sure I remember when it started. I've been living with it and finally decided to add issues so it could be fixed.