Customized style settings for font size in 3.5 are reset to 3.5 default upon import into 3.6

• Dec 31, 2020 - 18:39
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

  1. Open the attached file in 3.5.2 and the RC (without updating). Inspect the (1) Expession text and (2) text line. In both cases the font-size was set as style in a previous MS3 version.

Expected result: They should be the same size in both versions.
Actual result: They are larger in the RC.

  1. Inspect the Expression text and text-line font-size values in the Text style menu. Then in the Inspector.

Expected result: Font-sizes are the same in both versions in both the Style menu and the Inspector.
Actual result: In the RC, the Style menu is still showing the font-sizes from 3.5.2, which should have carried through to the document window. But, the Inspector is showing larger values which are the actual sizes in the document window.

Related to #315006: Headers in imported 3.5.2 files are lost (perhaps due to style properties being reset to default in the RC)?

Attachment Size
font_size_issue.mscz 10.61 KB

Comments

Title Style properties, changed in previous MS3 version, being reset to default in the RC? Customized style settings for font size in 3.5 are reset to 3.5 default upon import into 3.6
Severity S2 - Critical S3 - Major
Priority P1 - High

I can confirm this is not right on import and hopefully we can find a way to address this, although it's not "critical" according to the definitions we use. Realistically, there will likely be other differences as well as there have been some relatively significant changes. But again, it would be good to find a way to address this.

The default for expression text in 3.5.2 was 11 pt, but this score had customized that style setting to 10 pt. In 3.6, 10 pt is actually the new default, but when you decline the update, it seems we are forcing the old factory defaults rather than honoring what is in the file.