Position adjustments on text with Up/Down key is lost on save

• Feb 8, 2019 - 19:13
Reported version
3.0
Priority
P0 - Critical
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project

For explanation and details, see discussion in: https://musescore.org/en/node/283635#comment-893885


Comments

Status active needs info

I'm afraid I cannot reproduce using either 3.0.2 or my own build from master today. Can you please attach a score and give very precise steps to reproduce the problem? Like, tell me which fingering to move, which cursor key to use to adjust the position, how many "clicks" to move it, etc. I tried everything I could think of and could not get it to fail.

Now, that's weird, I tried again with the Tester file and now I can see a problem. I think maybe it's only on beamed notes? Anyhow, I can reproduce, will investigate.

Title Position adjustments on fingering with arrow keys are lost on save Position adjustments on text with Up/Down key is lost on save
Status needs info active
Priority P0 - Critical

How about this: Left & Right work fine, so does Ctrl+Up/Down, but Up & Down by themselves don't work (unless you also use one of the others)!

Also, it's not just fingering, but any text.

The other clue to a problem is that the Reset button in the Inspector doesn't activate.

In reply to by Marc Sabatella

Steps were simply:
1) Default score: Enter a quarter note top staff (so, no necessary beamed notes)
2) Double-click on "m" (RH fingering)
3) Immediatly: press arrow Up two seconds in a continuous way, so the "m" is closer the title frame
4) Save/Close
5) Reload: "m" reverted to its initial position

EDIT: and indeed, same behaviour after entering regular text (note -> Ctrl + T -> "m" -> Escape -> select "m" -> press Up arrow in a continuous way, etc. )

Yes, in case our posts crossed, I was able to ascertain that Up and Down do not work, but the other cursor commands (Ctrl+Up, Ctrl+Down, Left, Right, Ctrl+Left, Ctrl+Right) do. My PR fixes that, thanks for the followup!

Fix version
3.0.3