Fix #317426: Rests grouped incorrectly after adding 256th note or smaller #7518
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: https://musescore.org/en/node/317426.
The functions that deal with rhythm grouping operate on integer ticks, but they are smart enough to realize that integers can only be split in half so many times. If and when this limit is exceeded, populateRhythmicList gives up trying to group rhythms based on subbeats, and simply appends the result of toDurationList() to the current duration list that is being built. But toDurationList() returns a list that is ordered from largest to smallest, so it really ought to be appended in the reverse order.