Headers in imported 3.5.2 files are lost (perhaps due to style properties being reset to default in the RC)

• Dec 31, 2020 - 20:24
Reported version
3.x-dev
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.451380634, revision: 10dee08

Open the attached file. The page numbers were in the headers in 3.5.2, but they have been relocated to the footers in the RC. This is reflected in the Format > Style > Headers, Footer menu.

Could this be related to #315003: Customized style settings for font size in 3.5 are reset to 3.5 default upon import into 3.6?

Attachment Size
header_footer_issue.mscz 9.16 KB

Comments

Title Headers in imported 5.3.2 files are lost (perhaps due to style properties being reset to default in the RC) Headers in imported 3.5.2 files are lost (perhaps due to style properties being reset to default in the RC)
Severity S2 - Critical S3 - Major
Priority P1 - High

I think probably it is the same issue, but I also know text handling is different from other settings in terms of compatibility, so I'm not totally sure it's really the same.

My theory is this:

A bunch of style settings changed from 3.5.2 to 3.6, and that includes all text fonts (to Edwin), certain text sizes (mostly to make them a smaller point size), but also some things like header (it's where the page number goes by default), also slur thickness, minimum note distance, and a bunch of others.

It seems that perhaps any style setting you had changed in 3.5.2 but happened to change to exactly what the 3.6 default is, these settings are the ones being forced back to the old default when you decline the update. I think we are trying to restore the old defaults, but we must not be able to tell the difference between a style setting that is at the new default value on import because the user never customized it to begin with versus one that is at the new default value because the user did customize it, but changed it to the new default.