Dashed volta lines come back as continuous after the score is saved.

• Feb 8, 2021 - 08:21
Reported version
3.6
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
PR created
Regression
Yes
Workaround
Yes
Project

1) set a volta line over a measure
2) using inspector, change the line to dashed
3) save the score
4) re-load the score and the line will be changed back to continuous


Comments

Regression No Yes
Severity S4 - Minor S3 - Major
Type Graphical (UI) Functional
Priority P1 - High

Confirmed, with 3.6.0 and a 3.6.2 pre-release. And a 3.6 regression, works in 3.5.2

It does seem to get stored in the score though:

          <Spanner type="Volta">
            <Volta>
              <endHookType>1</endHookType>
              <beginText>1.</beginText>
              <lineStyle>2</lineStyle>                <<<<<<<<<<<<<<<<<<<
              <endings>1</endings>
              </Volta>
            <next>
              <location>
                <measures>1</measures>
                </location>
              </next>
            </Spanner>
 

3.5.2 does still show it (after having ignored the version warning)

Status active PR created

https://github.com/musescore/MuseScore/pull/7453

Also fixes similar issues with line width, and line width on pedal lines, and the mmrest number offset, and tuplet font settings. All stem from the same cause, failure to manage the property flags correctly, so these settings were never marked UNSTYLED.
This makes them susceptible to being lost on save/reload but also on any other style changes.

Workaround No Yes

There are a couple of relevant workarounds. In cases where you actually want to make a change to all voltas, you can hit the set as style button ("S" icon) - then the setting is remembered properly. But I guess you probably don't want all voltas dotted, just this special one. So instead, consider making not using a volta anyhow, but instead, a system line. You can add hooks as desired to make it look as much like a volta as you like, and since it won't play back either way, it shouldn't matter.

Right, when I made the fix for this, I went through and did a pass through other elements to see if I could find other cases of the same thing going wrong. Actually for mmrest number position it was worse, never even written, but even if it had been, the same bug would have occurred on save/reload without the additional fix.