BTW, you should also be aware that in 1.3, it is "by design" that text style changes don't change existing text (text already present in your score). You'll note that those changes don't apply to most other types of text either, even after a reload. So It's arguably a bug that the measure numbers *do* change after the reload :-). But not really; measure numbers are not really "existing text" in that they are generated on the fly depending on the layout of your score. For example, if you insert/delete measures, or the number of measures per system changes, this will normally cause measure numbers to be re-calculated/drawn anyhow.
I mention this just to avoid misunderstandings about how 1.3 is supposed to work. Normally, text style changes won't affect existing text, and that's not a "bug" per se - just the way it was implemented. But for 2.0, it's been re-implemented so text style changes *do* apply to existing elements (no reload required, either).
And so you know, in general, the issue tracker reflects the status not of the released version but of the development version. So bugs marked "fixed" aren't necessarily fixed in 1.3 - it means the fix is already implemented in the development version which will eventually becomes 2.0. Because of this, it is good practice to install a recent Nightly development build to test a behavior before submitting a bug reoport - chances are pretty good that, as in this case, the bug has already been fixed.
Comments
reload the score and it is applied.
A workaround is not a fix. The issue remains open unless and until OK and APPLY work.
And the nightly builds since Long, so will be fixed in the next release. Sorry, I should have mentioned that earlier
BTW, you should also be aware that in 1.3, it is "by design" that text style changes don't change existing text (text already present in your score). You'll note that those changes don't apply to most other types of text either, even after a reload. So It's arguably a bug that the measure numbers *do* change after the reload :-). But not really; measure numbers are not really "existing text" in that they are generated on the fly depending on the layout of your score. For example, if you insert/delete measures, or the number of measures per system changes, this will normally cause measure numbers to be re-calculated/drawn anyhow.
I mention this just to avoid misunderstandings about how 1.3 is supposed to work. Normally, text style changes won't affect existing text, and that's not a "bug" per se - just the way it was implemented. But for 2.0, it's been re-implemented so text style changes *do* apply to existing elements (no reload required, either).
And so you know, in general, the issue tracker reflects the status not of the released version but of the development version. So bugs marked "fixed" aren't necessarily fixed in 1.3 - it means the fix is already implemented in the development version which will eventually becomes 2.0. Because of this, it is good practice to install a recent Nightly development build to test a behavior before submitting a bug reoport - chances are pretty good that, as in this case, the bug has already been fixed.