musescore / musescore/MuseScore
System spacing changes unpredictable when adjusting Page Style
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Bug description
In single system scores, vertical spacing doesn't change accordingly to the values given in Style / Page dialog.
-
On first change of any vertical spacing value, the upper most system moves down by roundabout it's own height.
-
It stays there, even if you reset to default values. As like top and bottom position were mixing up.
-
This behavior doesn't switch back, even if you revert to default settings.
-
It doesn't matter if vertical justification is enabled or not.
-
If you reduce the systems spacing now, the gap between the both topmost ones isn't equal to the rest.
That happend with a new file.
Don't exactly know if it's the same. Maybe more or less related:
When I tried to open a Score created 3 weeks ago with the previous version, it looked all fine.
I changed the Title font and with that change, spacing was reset to default value (vertical justification off, default 15sp).
Originally it was much smaller due to space limitations.
When I reopened the file I found, that even in Style / Page dialog the default value of 15sp showed up.
I can change this value - it works as expected when increasing it, but decreasing below 15sp has just no effect.
Steps to reproduce
- Open New or existing Score
- Format / Style / Page
- Change Spacing Parameter, while have a look on top staff
- Reduce Spacing to minimum
Screenshots/Screen recordings
First, Spacing of Systems:
Second: Score File with Spacing Issue
Bannerlied_A5.zip
MuseScore Version
4.2.1
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Mint Linux 20
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.