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

Allow more flexibility for Spanners to compute start and end segment #18904

Conversation

mike-spa
Copy link
Contributor

@mike-spa mike-spa commented Aug 3, 2023

Resolves: #18644

As @cbjeukendrup said, the definitive solution to these kinds of bugs will come when we do #16796. In the meantime, this is still a good thing to do, i.e. make spanners more flexible when computing their start/end segment.

@mike-spa mike-spa force-pushed the fix#18644Crashwhenmovingtempolinesinparts branch from 21f6bd0 to 0b5131f Compare August 16, 2023 09:19
@mike-spa mike-spa force-pushed the fix#18644Crashwhenmovingtempolinesinparts branch 2 times, most recently from 5e3e80f to 9fd2fab Compare September 19, 2023 15:13
Start segment: if a segment is not found to the right of this tick, allow looking to the left.

End segment: system-line spanners should be allowed to terminate on segments that aren't necessarily ChordRest (for example, they can terminate on bar lines).

correction
@mike-spa mike-spa force-pushed the fix#18644Crashwhenmovingtempolinesinparts branch from 9fd2fab to bde4316 Compare September 25, 2023 12:46
@cbjeukendrup cbjeukendrup merged commit 35db753 into musescore:master Sep 26, 2023
11 checks passed
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.

Crash when moving tempo lines in parts
3 participants