Page settings don't apply to all parts when using "Apply" before "Apply to all parts"

• Feb 5, 2022 - 12:27
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

Steps to reproduce:
-Change Scaling factor for one part, press "apply to all parts" button
-Open different part; scaling has not changed.

Also, related:
I can't type a value in the Scaling Factor box, because when I delete a digit it's immediately replaced by 0. So, if I want to use factor 1,500 I select the current factor and start typing, but as soon as I have pressed 1 the box says 1,000 and I can't type anymore.

Attachment Size
Excelsior - Whitacre - October.mscz 220.03 KB

Comments

Yes, setting it in one part and using the Apply to all parts button, and that does, correctly, change if for all parts.

The other issue is know IIRC

It doesn't work in any of my scores so far.
I just realised I made a mistake though; I am using Windows 11 since a few weeks, not Windows 10. Could that make a difference?

Found out something: it matters in which order I press "Apply to all parts", "Apply" and OK. "Apply" and then "Apply to all parts" doesn't work, the other way around it does.

Workaround No Yes

OK, that may explain it, after Apply it sets if for the current part, but then the Apply to all parts has (or ratjher: thinks to have) no changes to apply anymore. So the workaround is to not use Apply, but Apply to all parts.
And you never mentioned that extra step of 'Apply', so no wonder it could not get reproduced ;-)

Title Scaling Factor settings don't behave as expected Scaling Factor settings don't apply to all parts when using "Apply" before "Apply to all parts"
Status needs info active
Title Scaling Factor settings don't apply to all parts when using "Apply" before "Apply to all parts" Page settings don't apply to all parts when using "Apply" before "Apply to all parts"

Regarding the typing - you can typoe, but indeed it needs to be one digit at a time, selecting the old digit and typing over it. And yes, it sucks, but already fixed for MuseScore 4.