Can't reduce layout stretch via shortcut - Invalidity of shortcut

• Jul 9, 2019 - 14:40
Reported version
3.x-dev
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project

If you press the shortcut "{", you can't reduce layout stretch. This issue still exist even if I have customised more or reset the shortcut, it’s still not working. The only workaround so far is to mannually make it from the menu. However, increase layout stretch is available by both ways.

} can work while { can't

Happens on

  • Qt 5.9.8
  • OS: macOS 10.15,
  • Arch.: x86_64,
  • MuseScore version (64-bit): 3.2.3.22971 (d2d863f)

Hardware Details

  • Terminal Model: MacBookPro
  • Keyboard Quality: Fine and normal (When you are setting the shortcut, it can recognise the key)
  • Keyboard Layout: QWERTY

Reproduction

  1. Use the sample file
  2. try to reduce stretch with "{" you'll find you can't.
    (To make the sample file, I used the shortcut "}" to increase layout stretch. Try to reduce it. )

Details of the sample file

The sample .mscz file was written by me, MuseScore user David Copperfield, who rearranged H. P. Lovecraft Historical Society's work.

Attachment Size
LayoutStretchHasProblem.mscz 17.82 KB

Comments

Status active needs info

What happens when you try to assign { as a shortcut for the action via Edit > Preferences ?

As always, sample score and steps to reproduce the problem would be useful. Also, say what you have tried changing it to - it could be indeed that you just happened to pick another combination not recognized as expected by your OS / Qt. To be sure, try more custom shortcuts, including ones you have verified do work when assigned to other commands.

Status active by design

Which measure of measures were you selecting when decreasing stretch? I didn't find any problem with any of the measures I tried, but I did have to decrease about 30-40 notches before I saw anything happen, because you've increased the stretch by equally crazy amounts. Go to Measure Properties to see the stretch values you have defined - the default is 1, you have it all the way up above 4 in many measures, and the step value is 0.1.

Best t simply select all then reset the stretch to start over whatever you were trying to do.

Title Can't reduce layout stretch via shortcut Can't reduce layout stretch via shortcut - Invalidity of shortcut
Status closed active

It could take place on every mesure. I want to modify each instead of to reset. You’ll find that you can’t reduce it with shortcut. I understand the case if you have increased too much, the reduction may seem to do nothing to layout. This issue is about the invalidity of shortcut.

Status active closed

Please read my explanation above in full. You have increased stretch to such an extreme degree, you will need to reduce it by up to 30 or notches before you will see any effect, but it's working exactly as it should. It was a mistake to have increased stretch so much - once you increase it so much that only one measure fit per system, the additional increase did nothing but make it harder to reduce later. That is why I think you should start over, because the score is in a very messed up state right now that far longer than it should to correct. But if you wish to do so, start by reducing stretch 30 notches.

Status closed active

If it could work, I wouldn't annoy you any more (My apology). I use this function very frequently since 2.0, thus I understand what you have said. I seriously hope you try this version on Mac. I can't use the shortcut even if I have replaced or reset it. This is a matter of shortcut.

Does the attached file work for you?
Select measures 1-11 (all those with notes).
Reduce stretch once; measure 10 should now jump back to system 1.

Please go to Edit → Preferences… and in the shortcuts tab press the Save button.
Attach the resulting shortcuts.xml file here.

Attachment Size
stretch.mscz 5.46 KB
Status active needs info

I don't have a Mac, but I know the code well enough, and can see what's going on in your score clearly enough, that I am still quite confident I am right.

So, please humor me and try the following:

1) open the score
2) reset the shortcut to the default, or set it to something you have verified works for other commands (and tell me what it is)
3) right-click measure one
4) Measure Properties
5) confirm you see the entirely inappropriate value of 4.20 for Layout stretch
6) OK
7) with the measure still selected, press your shortcut exactly 20 times
8) go back to Measure Properties
9) check the value of Layout stretch

If I'm right - and I'm quite confident I am - you will see the stretch is now 2.20. Still insanely high, which is why your reducing of stretch hasn't worked yet.

Now, reduce stretch 12 more times (there could be font differences between systems here, maybe it will take 13 or 14. You should finally have reduced stretch enough to actually cause the next measure to fit on the first system. And if you go to Measure Properties, you'll see the value of "Layout stretch" is now 1.00, which is where it would have been had you followed my advice to reset stretch in the first place :-)

All of this is exactly as it should be given the completely inappropriate amount of stretch that was already preent. It really does take 32 presses to get it back to normal.

BTW, please do not change the status of this (or any) issue from "needs info" until a developer is able to confirm and reproduce the problem.

Frequency Once Many
Status needs info closed
Reported version 3.2 3.x-dev

This issue is finally fixed in 3.3 unstable prerelease build (OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.3.0.23299, revision: dcf26e7)

To be clear, for others following the discussion or who might land here later: it is virtually certain it was never broken. Try the precise steps I listed above with the attached score and you will see it is exactly as I said. It is important people realize this, because it is easy to get yourself into a situation where it appears the shortcut doesn't work, but I assure you, it does. and always has. The steps I list produce exactly the same results in 3.2.3 and development builds of 3.3 as well as every previous MuseScore 3 release.

That being said, reducing stretch often seems to work much less often in 3.x than it did in 2.x (at least if you select multiple measures worth, i.e. a whole line in order to make place for just one more measure), or at least really differently…

@mirabilos the stretch algorithm is different to be sure, but probably more to to the point, so is pretty much everything else about layout, so it could be the passage in question simply takes more space than it might have in a previous release that, for instance, allowed collisions, or didn't reserve space for lyrics hyphens, etc. Feel free to start a new forum discussion with a specific score for us to look at.