Custom text ignores system flag when imported into 3.x

• Jan 19, 2019 - 19:42
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

When you create a custom text style in version 2.x, then import the score into version 3.0.1 the system text flag is ignored. When it encounters a custom style, the text needs to be examined to see if it has the system text flag set. In this case, system text needs to be entered into the imported score.

The workaround is to delete all improperly imported text. create a new custom text style, add system text again and select that style in the inspector.


Comments

There is a TODO in readMeasure(0 in read206.cpp in the code dealing with "StaffText" (which is what system text really was in 2.x) indicating this is a known limitation. Right now, we only recognize system text in a 2.x file as being system text by the actual name of the text style - it has to literally be "System" or one of the other known system-ish types like "Tempo" or "Rehearsal Mark". Ideally we'd be able to match up the style name with the actual style at this point and check its system flag, but I don't know how feasible that is.