Page Settings, scaling "Stave Space" figure cannot be edited in normal ways

• Dec 2, 2019 - 08:23

On Format/Page Settings, the Scaling of the Stave Space figure is hard to edit or change. The little arrow buttons to raise or lower the size do intelligently alter the size of the Stave Space. They work in the way they used to in Musescore 2. However, I often use this scaling to make the whole score fit better on the pages with no "hanging" bars at the end of the piece, by changing the number (in mm). So I want to change the intelligently suggested figures to my own whilst watching the overall page fit. I could easily change the figures in the Stave Space box in Musescore 2, but cannot do it without problems in Musescore 3.

If you try to edit the number in the box, the format of the field does not allow normal edits. For example, the "Equus, full orchestra" score in your sheet music downloads initially shows a scaling of 1.150 mm on my computers. But if you edit this value, odd things happen. If you backspace out the 5 digit, you cannot replace it with a different digit. Indeed any digit to the right of the decimal point gets replaced with a zero and cannot be changed. This did not happen with Musescore 2! There is something odd about the formatting of this field in Musescore 3.

This little buglet appears on all my scores, both downloaded or created by me.

Derek


Comments

In reply to by geetar

I am just a simple user of Musescore and this link shows me that someone is trying to do something about it (sadly with a lot of unintelligible - to me - computer software development jargon).

However, despite acknowledging the buglet, it is not solved yet. Is anyone likely to do anything about it, please? It would be lovely for the functionality of the Musescore 2 program to be copied into this part of Musescore 3. Is this possible?

In reply to by [DELETED] 7670311

It is not yet fixed in any released version of MuseScore, nor in any development build.
A fix is known though, it just needs to get checked further and then integrated into the code.
That is what "Status: patch (ready to commit)" is supposed mean.

Actually that patch doesn't apply cleanly to the current codebase anymore, so it needs more work.

In reply to by Jojo-Schmitz

The patch in question does a ton more than just fix that input field. I don't understand all the issues involved with the rest of the changes. But I'd certainly love it it if someone would just implement a fix for that one input field, without saddling it with a bunch of other unrelated code. Then it would likely be merged immediately.

Do you still have an unanswered question? Please log in first to post your question.