pagesettings: modify height switches to width, changes orientation

• Nov 24, 2018 - 18:15
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

I find it hard to believe that I could not find an issue already posted for this. It is an extremely annoying bug. Open any score. Go to Format/Page Settings... and modify the value for Height by typing a number or pressing . Instantly the height and width switch values, and the orientation flips between portrait and landscape as appropriate. This does not appear to be happening inside the PageSettings::updateValues() so much as in the layout procedures that follow, though I've just gotten up and running with VS2017 on Windows 10, and my debugging skills here might be weak. The width and height variables "w" and "h" in updateValues() are correct until the end of the function, AFAICT.

What makes this bug so annoying is that the focus stays in the height field, but it's now filled with the width's value. So you start typing a height value, and next thing you know you are editing a different value.

Note that these fields default to mm and the maximum value is 2,000, so in most scores you cannot simply type an additional number into the height field, as 200mm is not a large page size, and you would be exceeding the max value. So I suggest deleting a digit, or selecting over the whole number and typing.

That max of 2,000 in the width and height fields is too low, IMO, but that's a separate issue to be filed.

Comments

• Nov 25, 2018 - 00:44

I should add that I noticed this behavior months ago, but I wasn't using MuseScore much at the time, and 3.0 wasn't in an alpha stage. I believe the issue dates back at least 6 months.

Reply

• Nov 25, 2018 - 07:28
Priority P1 - High ⇒ P0 - Critical
Severity S3 - Major ⇒ S1 - Blocker

Increasing Severity and priority, we can't release a beta with that.

Reply

• Nov 25, 2018 - 15:08

Now you can understand my surprise when I saw this bug still active six months later. I should have reported it immediately, but I figured the code was undergoing changes and someone was bound to see it, if they had not already. I must be one of very few people using custom page sizes. I hadn't thought about it in terms of quantity of use before, but now that I think about it, I can understand why most users don't touch these settings.

Reply