text: Fix x/y scaling of device text glyphs #22209
Open
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
kjarosh
added
text
Collaborator
|
This also fixes #16745! |
kjarosh
force-pushed
the
edittext-device-transform
branch
from
e0d59aa to
798f205
Compare
This is needed as this transformation applies device-text specific scaling.
This makes sure that the device-text specific transforms are applied.
Device text requires non-translation-only transformations in the layout_to_local_matrix, which requires the generic inverse() function to be called when calculating its inverse.
Device text in FP cannot be scaled independently in x/y. Only the y scale is applied, and the x scale is set so that the aspect ratio of characters is preserved. It's used only for calculating metrics and sizing bounds.
Tests basic translations applied to device text.
kjarosh
force-pushed
the
edittext-device-transform
branch
from
798f205 to
eaf94dc
Compare
Collaborator
|
With this, #22113 displays this: The text is no longer stretched, but it's not in the right place anymore. |
|
@kjarosh @Lord-McSweeney IMHO, i don't think is due to this PR because is already happens in this following example where text is getting behind the input field : https://mep-col.sesamath.net/dev/swf/exo657.swf?idMep=91&modeleMep=1&abreviationLangue=fr&idSwf=91&ch=n&idAide=79&isBoutonSuite=o&isBoutonAide=o |
Lord-McSweeney
approved these changes
Dec 9, 2025
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.
MOUSE_OUT->gotoAndStop()causes text to vanish. #15110Device text in FP cannot be scaled independently in x/y. Only the y scale is applied, and the x scale is set so that the aspect ratio of characters is preserved. It's used only for calculating metrics and sizing bounds.
This PR contains a bunch of patches that bring us closer to FP's behavior. We're still not perfect, especially related to measurements, but the good news is that it's a mess in Flash Player too, just a different one.
The main issue with dependent x/y scaling is that measurements operate in unscaled coordinate space, meaning that we have to emulate the size of the unscaled glyphs. If
scaleX/scaleY == 0.5, we have to act as if glyphs were twice as wide.After this PR Ruffle still behaves differently, especially related to: