Fix crash on deleting MMR time sig #32104
Open
+604
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #32017
When creating a
ScoreRange, we provide a firstSegmentand a lastSegment. The last segment is not added to the range and is not copied. It is only used to calculate the range's length in ticks.When opening a file containing MMRests, we don't lay out the underlying measures. This means time signatures and end barlines are not generated. The underlying measure only contains 1 chord rest segment.
ScoreRangeneeds at least two segments to calculate the correct number of ticks.This PR makes sure we calculate the number of ticks a range covers correctly when deleting time signatures.