Ties sometimes do not respond to Inspector offset adjustment until editing completed
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6052, revision: a9df4a0
Open the attached file and take the reset. Click on a note tie and use the Y-offset in the Inspector to move it downwards.
Result: It stops at 0.5sp. If you move it beyond that point, then press [Esc] (or click on a blank space), the tie will suddenly jump to the new position. You have to save and reload the file to restore correct functioning.
| Attachment | Size |
|---|---|
| temp.mscz | 10.1 KB |
Comments
What I see is that the tie doesn't move at all until I leave the spinbox, but at that point, the offset is applied normally. The results are the same for brand new scores as imported ones.
Are you seeing something different? If so, how exactly are you entering the offset into the Inspector?
I should have been more specific. The OP was using the Inspector Y-offset spinner, rather than directly modifying the value.
Whatever method you use, the same score, created from scratch in 3.x, behaves as expected: the tie moves downwards as you increase the y-offset. Immediately saving and reloading the attached 2.x score also gives the expected behaviour.
The problem occurs only in imported 2.x scores.
Interesting, I can actually reproduce this from scratch in 3.0 as well, at least sometimes - not exactly sure what the trigger is.
But the more important point is - for me, the tie updates instantly as soon as I leave the Inspector (eg, click anywhere else). Both in this score and any other score I can reproduce this behavior in. As such, it's a lot less severe than if it truly requires save/reload before the tie moves. But, I think maybe I misread the original report then - you weren't saying you needed save/reload just to see the change, but that save/reload causes the tie to respond more quickly. In which case, we are seeing more or less the same thing then.
It was the title that confused me I guess.