fix #35176: ottava layout in various special situations #1364
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.
The issue reports one particular case where the endpoint of an ottava line was not calculated well, but in investigation I found a number of others. The code was relying on the width of the segment containing the last chord, and and that probably should work, but there are actually a number of case where the segment width is not set correctly. So instead of using the segment width, I now loop through the chords in the segment myself and find the rightmost point. I left the original code in place (ifdef'ed out) so we can switch back if we fix the segment width issues. But there are a few other small fixes to line layout in this PR we'd want to keep in any case.