Score glitch

• Jan 6, 2021 - 10:32
Reported version
3.5
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Once
Status
closed
Regression
No
Workaround
No
Project

this randomly happend.

Attachment Size
glitch.PNG 49.74 KB
zw.mscz 19.91 KB

Comments

Status active needs info

There one occurence of

          <Segment>
            <leadingSpace>152.565</leadingSpace>
            </Segment>
 

in the score, in that very measure 9 and the top staff and the first note, a Sebment Space left setting offset of 50sp.
Removing that seems to fix the score, check the attached.
Question is: how did it get into that state?

Attachment Size
zw.mscz 20.96 KB

To fix it yourself select the last note of measure 8 in the top staff, use the right arrow to move to the next note and then in Inspector reset the the Segment setting from 50sp back to default, 0