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

Fix computation of Spanner start element in presence of MMRests #20346

Merged

Conversation

mike-spa
Copy link
Contributor

@mike-spa mike-spa commented Dec 6, 2023

Resolves: #20337
Resolves: #20340

@zacjansheski
Copy link
Contributor

Tested on MacOS 14, Windows 11, Ubuntu 22.04.3. Approved
#20337 FIXED

@mike-spa
Copy link
Contributor Author

mike-spa commented Dec 6, 2023

@zacjansheski I've fixed another closely related issue, let me know if it all work alright!

@mike-spa mike-spa force-pushed the correctSpannerStartElementComputation branch from c801943 to 610da9c Compare December 7, 2023 08:28
@cbjeukendrup cbjeukendrup merged commit aa34243 into musescore:master Dec 7, 2023
@RomanPudashkin RomanPudashkin mentioned this pull request Dec 11, 2023
@mike-spa mike-spa deleted the correctSpannerStartElementComputation branch February 17, 2025 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trill accidental visibility reset inconsistent Trills do not appear in custom parts
4 participants