New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Music should automatically clear headers and footers #9193
Music should automatically clear headers and footers #9193
Conversation
Some test failures, crashes actually |
fix style changes fix failing tests
7940ebf
to
87b19c9
Compare
Fixed the failing tests. Edit: for some reason, the tests are passing on my machine but are failing on CI. Working on figuring out why that's happening now. |
87b19c9
to
9af65f9
Compare
For me it crashes whan opening an existing score, and with a failed assertion: Fatal: ASSERT: "!strcmp(MStyle::valueType(idx),"Ms::Spatium")" in file .../libmscore/score.h, line 896 So it got to be in layoutpage.cpp, where you're using |
9af65f9
to
b5a298b
Compare
Backport of musescore#9193, part 1 and 2
Still fails |
add x,y coordinates to Sid::headerOffset fix failing CI tests fix CI test errors
b5a298b
to
37e8cbe
Compare
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Hi @Nick-Mazuk , should it work like this? |
No, that's a bug. Thanks for finding it, I'll fix it! |
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Backport of musescore#9193, part 1 and 2
Cool! Then just assign to me when it's ready |
fix style changes fix failing tests
add x,y coordinates to Sid::headerOffset fix failing CI tests fix CI test errors
fix error with justified systems fix header collision with vertical frame remove footer collisions with vertical frames remove useless space remove extra space added between footer and justified systems
Oh, I see what you mean now. From the video, that is the behavior I'd expect, though I can see how someone would not expect that behavior. I'll double-check with Simon when I speak with him tomorrow to confirm the desired result. |
…MuseScore into header-footer-margin
The Merge commit doesn't belong into this (or any) PR |
The behaviour with regard to page breaks seems as I would expect: a page break simply means that the next system will be on the following page, but it can't force more systems to fit on the preceding page than there is space for. There's scope for some sort of "keep systems together on page" functionality in the future (analogous to "keep bars together on system") but that would be an entirely separate issue from this. |
Backport of musescore#9193, all 3 parts
Backport of musescore#9193, all 3 parts
Got it. Thanks for review Simon! Lets merge it into master |
Backport of musescore#9193, all 3 parts
Please merge into master (@RomanPudashkin ) |
Backport of musescore#9193, all 3 parts
Backport of musescore#9193, all 3 parts
Backport of musescore#9193, all 3 parts
Resolves: #9043
Resolves: #9340
Resolves: #9159
This PR removes collisions between headers/footers and music. When header or footer text becomes too tall, the music will automatically move out of the way.
Here's a diagram of what's happening:
header-footer.collision.avoidance.mov