Skip to content
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

Extending minimum tie length implementation to apply at start of system #12451

Merged
merged 2 commits into from
Jul 20, 2022

Conversation

mike-spa
Copy link
Contributor

At the moment, minimum tie length is only enforced between adjacent chords. That was by design in my first implementation. @oktophonie pointed out that it can be necessary to enforce it also at the start of a system. That case requires special handling, which is now implemented.
Additionally, the space between the end of the header and the start of the tie (which used to be determined by an anonimous variable set to 1 sp) has been moved into a dedicated style setting (though not exposed in UI).

Before:
Immagine 2022-07-15 181819

After
Immagine 2022-07-15 182043

@oktophonie oktophonie added the vtests This PR produces approved changes to vtest results label Jul 18, 2022
@mike-spa mike-spa changed the title Entending minimum tie length implementation to apply at start of system Extending minimum tie length implementation to apply at start of system Jul 18, 2022
@oktophonie oktophonie added this to In progress in [MU4.0 - ENGRAVING] via automation Jul 18, 2022
endNote->addLineAttachPoint(ups(Grip::END).pos(), tie());
}
startNote->addLineAttachPoint(ups(Grip::START).pos(), tie());
endNote->addLineAttachPoint(ups(Grip::END).pos(), tie());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the null-check no longer needed here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. In principle, the null-check isn't strictly necessary, because startNote and endNote are never null. But I think it's safer if I null-check anyway, just in case we encounter a broken tie or something. I'll quickly fix this

[MU4.0 - ENGRAVING] automation moved this from In progress to Reviewer approved Jul 20, 2022
@RomanPudashkin RomanPudashkin merged commit 4e127ad into musescore:master Jul 20, 2022
[MU4.0 - ENGRAVING] automation moved this from Reviewer approved to Done Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engraving vtests This PR produces approved changes to vtest results
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants