Version 3.6 and styles
Hi.
I cannot find the "old" "reset style" option on V 3.6. Is it removed?
Another "issue" is that when I try to load a style MuseScore says: "The style is not compatible with this version of MuseScore." Should not a newer version be able to handle older styles?
Comments
Open the style file with a text editor and change the 301 to a 302
In reply to Open the style file with a… by Jojo-Schmitz
Ok, thanks. I will do that, but I guess many users may have the same issue,
Perhaps Musescore could do this automatically?
In reply to Ok, thanks. I will do that,… by ErlingI
IIRC we did allow to open downrev mss files, not sure why we don't any longer?
Edit: actually we still do, you'd just have to use the "Ignore" button
In reply to IIRC we did allow to open… by Jojo-Schmitz
Thanks again for your response! I (of course) used the Ignore button, no problems there, but I guess MuseScore should "fix" the issue for the user "behind the scene" so the "issue" does not "pop up" every time.
And the "reset style" was an option before. Is it "gone"?
In reply to Thanks again for your… by ErlingI
It is a different version and that downrev mss file might not fully work, hence the warning is in order.
Not sure what "reset style" option you mean?
In reply to It is a different version… by Jojo-Schmitz
In 3.5.2 (and earlier versions) there was an option under the format menu: “Reset style”. I cannot see that option anymore.
In reply to In 3.5.2 (and earlier… by ErlingI
Hmm, there's "Reset Text Style Overrides" now, and also in the Edit Style dialog at the bottom "Reset all style values to default"
In reply to Hmm, there's "Reset Text… by Jojo-Schmitz
The "reset styles to default" does not take into account my style defined in the preferences / score / style.
Is it because I still have it defined in the "old" 3.5.2 version?
Apart from that the style "reset option" it's "one level down" in the menus compared to earlier versions.
I wonder for what reason. It is/was most useful.
In reply to The "reset styles to default… by ErlingI
The old "reset styles" did two things - it reset everything in the styles dialog, and it reset everything in the page settings dialog. There were complaints that you might want to reset one but not the other - in particular, it's common in some circles to want to reset styles but keep page / margin sizes. So, we separated this command into two separates ones, one for each dialog.
In reply to The old "reset styles" did… by Marc Sabatella
Thanks a lot, most clarifying!
In reply to Open the style file with a… by Jojo-Schmitz
I received the warning that the style I wanted to load was not compatible with the current version of MuseScore. I chose "Ignore". I then saved the style under a new name. When I load the new style file I do not get the compatibility warning. I don't know if there are any bad surprises waiting for me, but I hope that saving the style file under the new version of MS will make it compatible.
In reply to I received the warning that… by David Mayerovitch
It should. The warning shows because down-rev version may have settings that no longer exists, or got changed, in a later version. It was deemed more suitable to emit that warning rather than refusing to load it at all.
A small "summary on this topic:
Jojo-Schmitz's solution to edit the style-file in an (text)editor and change from 3.01 ->3.02 fixes the style issue.
However, this should be done "behind the scene" by Musescore, in my view.
Regarding the "loss of" Format/"reset style" I, in my case, added a shortcut for "Reset style" in preferences/shortcuts.
The old "Format/ Reset style" is now found under Style "Reset All styles to Default".
In reply to A small "summary on this… by ErlingI
No, it remains an older format file and as such the warning that shows on 'impüorting' it is completly OK and in order. Pick "Ignore" and hope for the best (I don't see anything bad that might be happening though)
In reply to No, it remains an older… by Jojo-Schmitz
Hi and thanks for swift answers/comments. No big deal this, but in my opinion why not get rid of "noice" like this in the user-interface when a "fix" is easily available.
Allthough ignore is OK ("hope for the best" is not a software solution:) ) and probably does "no harm", the 3.01 - 3.02 fix might as well be put in place not to make (many?) users wonder "what is wrong?"
In reply to Hi and thanks for swift… by ErlingI
The fix is not easily available. A full fix would need to check every sing setting in the mss file whether it still exists and still has the same meaning. And it would need to differentiate between MuseScore 1, 2 and 3 mss files for that. The development resources are better spent elswhere than for a rather rarely use feature like style files in general and importing them from a downrev version in particular
In reply to The fix is not easily… by Jojo-Schmitz
Ok, I thought it was only a version number change, so I´ll rest my case.
In reply to Ok, I thought it was only a… by ErlingI
It might be only a version number in this particular case. But even testing whether that's really the only change is cumbersome. And would need the change from 301 to 302 to be special cased.
In reply to It might be only a version… by Jojo-Schmitz
(....deleted..)should be for Sabatellas comment!