Importing a 2.x score makes initial clefs lose their customized properties

• Nov 19, 2019 - 09:33
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
PR created
Regression
Yes
Workaround
Yes
Project

When importing a 2.x score where the initial clef of any staff/part has been set to invisible, this setting gets in 3.32 (at least)

Workaround: make invisible after import

Came up as a side issue of #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef


Comments

I cannot find why, I saw in the debugger that setFlag(ElementFlag::INVISIBLE, !f) was clearly executed, with f being false.

Title On importing a 2.x score, an initial clef looses its 'visible' property Importing a 2.x score makes initial clefs lose their customized properties