Fix #300340: Additive Time Signatures Do Not Appear Properly in the G… #6524
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.
…onville Font
Resolves: https://musescore.org/en/node/300340
Fixes a series of problems with spacing in which a sequence of glyphs is drawn as a string, and in particular, the 'advance' space value that was set to zero in case of a fallback glyph.
This includes sequence of time signature glyphs in certain fonts including Goinville, some sequences of glyphs that build mordents and ornaments, and some problems with dynamics with more than one glyph (ppp, fff).
For horizontal spacing:
_Found a call to ScoreFont::advance() that pointed to an override version that didn't compute the advance value from the fallbackFont. Because of this, the missing + glyph was drawn from the fallbackFont but its advance was set to zero.
For vertical spacing (when stretching the time signature):
_Found a call to ScoreFont::BBox() that pointed to an override version that didn't allow scaling in different horizontal and vertical dimensions.