Text styles not applied after Load Style...

This bug #118731: Text styles not applied after Load Style... was a duplicate of this one.

Rather #152921: Text styles do not update when loading style :-)

And came up yet again in https://musescore.org/en/node/152966
And in https://musescore.org/en/node/152806 before that

IMO what is needed is that when the style of a particular score is saved (presumably to be used again later as a template) then every characteristic of that score (except the specific notes and values particular to that score) should be saved and should load into a new score in their entirely when Load Style is clicked and the style in question is selected.

I am referring not just to text style but also other score attributes that the user may have selected and included, such as Tools setting for measures per line, size and positioning of rehearsal marks and page numbers, etc. Everything.

I agree with this.

Line breaks aren't settings, though - they are are actual elements added to your score, like notes and dynamics and lyrics. All actual settings *are* saved, but score content is not, nor should it be.

Size and positioning of rehearsal marks, page numbers, etc *is* controlled by style settings, though, so these already are saved as part of your style.

"Line breaks aren't settings, though"

Well, then, IMO they ought to be regarded as such (at least as an option) so that they can be incorporated into a template. Line breaks are page layout or format. They are not at all in the same class as notes, dynamics, lyrics, etc. which are specific to the particular musical piece in question.

You can't pretend something is something it isn't. A setting is something that is a single number or other value that applies to the whole score. Line breaks aren't like that, and *cannot* be like that in general. I guess you are in the habit of always inserting them every four bars, but the vast majority of scores are not like that. They have different numbers of bars on different lines, which requires actual line breaks to be inserted in the score to lock in if you don't just want to go with the default layout. Even for lead sheets that are "mostly" four bars per line, very often the first line has 5 to account for the pickup, also there might be 5 or 6 if there are voltas, maybe fewer bars on the last line before a coda, etc. That's why line breaks are inserted individually, even if there is a command to automate the process to get you started,

You seem to be talking in circles in your defence of the status quo, which I don't understand. I never suggested that a template should be carved in stone and not capable of being overridden as desired.

I have nothing further to add. We will have to agree to disagree.

Well, I think you are misunderstanding what I am saying, then. Yes, you can override settings. But if something is a setting, it applies to the whole score. So if you had a setting of "break every four bars", you could override it by changing to 3 instead of 4 so now you would have lines break every 3 bars for the entire score. But there would be no way to override it on a line by line basis, which is what would actually be needed.

Not that it would be impossible to redesign the layout algorithms of MuseScore so that you could have a setting to control the defaults and then also provide some brand new mechanism to override this line-by-line. But that would be an enormous undertaking for almost no benefit when it takes all of *seconds* to add line breaks currently. So as this stand now, without a major change to the layout algorithms and the addition of a new facility to override this line-by-line, there is simply no way to treat line breaks as a setting.

I take your point. I will mess with the template saving function and see how that develops. Thank you.

Huff?? Passing on this low-hangng fruit.

FWIW, further discussion of this topic is certainly welcome, but it should take place in the forum, in a new thread devoted to the topic.

Uncertain how this differs from #102716: Font doesn't automatically update itself after loading style.

This is fixed together with #102716: Font doesn't automatically update itself after loading style. I cannot reproduce in current 2.1.

Seems not fully fixed, see https://musescore.org/en/node/152746#comment-664186

I'd be happy to contribute as a tester.

Could someone provide a sample score and precise steps to reproduce whatever is believed to still be broken?

Here's a detailed description of some remaining issues, see MSCZ_TextStylesNotApplied.doc.
The other attachments can be used to reproduce the examples.
Let me know if I can provide further assistance.

Somewhat similar issue: #180846: Existing voltas do not obey text style changes

Similar but not the same.
This issue ("text styles not applied") reports that style changes from an mss file are not applied. Changing them in the text style window works correctly.
Your issue ("voltas do not obey...") reports that for extisting voltas a style change in the text style window is not applied.
This works: select the volta(s) that you want to change and apply your changes in the inspector.
Try also: Right click a volta and take a look at the select options in the context menu.

Indeed—if it was the same I wouldn't have made a unique bug report. ;-)

Are we talking about 2.1 or master? I am testing with 2.1.

If I understand correctly, the only two problems reported in the document posted above are with respect to chord symbols and tempo, is that correct? Specifically, after a load of a text style that changes the text style for those two types, existing elements of those types are not updated, is that correct?

Using 2.1, I can verify this for chord symbols, but not for tempo. The tempo marking in your sample score *was* updated - it moved much higher just as the style file you created calls for. And if I edit the style file to also change the size, that is honored as well. If you are still seeing problems with tempo in 2.1, can you just post specific steps to reproduce right here in a comment?

As for chord symbols, that I can reproduce in 2.1. Pretty sure the issue is that we need to call "render()" on the harmony elements after a style change, because chord symbols are not simple text and much needs to be recalculated about them after any style change. I think we do this for the General style change within Harmony::styleChanged(), but not the Text style change.

I tried to put down everything in detail in MSCZ_TextStylesNotApplied.doc.
I used MuseScoreNightly-2017-03-08-1741-2.1-7a20001 for all the test steps.
I tested only those style changes that I need for my current conversion project.
The behaviour is different if I apply my pgh_style_nightly.mss by calling "Load Style..." from the menu or by trying to apply it by calling it with the -S option on the command line.
The style for chord symbols is not applied in both cases. The style settings for tempo are applied correctly when calling the .mss file from the menu but NOT when the style file is called from the command line.

Is there still info needed?

I'm still unclear on how to reproduce a problem with *tempo* specifically, in 2.1, or if it is being claimed the problem is only in master. I *think* the claim is that the problem is only master, and only with command line invocation via "-S, but that wasn't totally clear to me from the document.

That's why, *if* it is being claimed there is a problem in 2.1, I could use a new set of steps directly here, something very simple like:

1) load attached MSCZ file into 2.1
2) load attached MSS file
3) observe that tempo is not updated

Again, when I try that with the MSCZ file and MSS file attached to response 20, it works - the tempo *is* updated. So we still need info on whether or not it is being claimed there is a problem with 2.1 and tempo. If it *is* being claimed, could new test files that clearly demonstrate the problem using the above steps (or whatever other steps are necessary in order to see the problem) be provided?

Just take the files already provided and apply the .mss file by calling MuseScore on the command line:

nightly.exe "Ap Shenkin.xml" -o "ApShenkin_5.mscz" -S pgh_style_nightly.mss
nightly.exe "ApShenkin_1.mscz" -o "ApShenkin_6.mscz" -S pgh_style_nightly.mss

When doing that, tempo is NOT updated.
When applying the same .mss file by calling "Load Style..." from the menu tempo is updated correctly.

OK, thanks, I can confirm that with 2.1. Not sure why tempo is special here.

One more thing: after
nightly.exe "Bielbie_s Hornpipe.xml" -o "Bielbie_s Hornpipe.mscz" -S pgh_style_nightly.mss
the vertical position of voltas in the mscz is set to 0. It is taken neither from the mss file nor from the default setting in MuseScore.
The same happens when I open an XML file from MuseScore's menu File > Open...
I would like to have the possibility to specify the volta position while converting xml to mscz.

The status of this issue is still "needs info" / "unassigned"
Can I expect it to be fixed in 2.1?
Does it make sense if I test it in the 2.1 RC? (probably not yet)

If this is fixed in 2.1-RC, then by accident.
Nothing related is mentioned in the (draft) release notes

Thanks for updating the status.

Came up again in https://musescore.org/de/node/187466

Came up again in https://musescore.org/en/node/267668

Is somebody working on this issue?
With a recent nightly build of V2.2 "load style" from the menu works fine.
But the issue with the command line that I reported 2017-03-13 is still unresolved. The same problem that I reported for "Tempo" also exists for "Title", "Subtitle" and "Composer": font settings are not taken over when "Load Style" is called via -S option on the command line. The same .mss file loaded from the menu works fine.
This is very annoying when I want to apply the same style to many songs. Currently I'm modifying a complete book with 200+ song files.

Since the remaining issue you are talking about seems to be with the command line interface only, it's a separate issue, and should be filed as such. Please open a new issue with a sample score and precisely step by step instructions to reproduce the problem, listed directly in the issue itself. That will make it much easier to investigate and track and will greatly increase the chances of this being addressed for 2.2.

FWIW, another way to make mass changes via the command line would be with a Perl script or some such to modify the MSCX file directly.

Filed as https://musescore.org/en/node/269491

Thanks!