You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In GlideImage, the implementation of ContentScale is with a contentScaleTransform.
This causes a few issues:
The same image with different content scales applied will have multiple memory cache entries.
It is currently not possible to interpolate a content scale change.
Ideally the application of a content scale should not require the creation of separate images. The same image should be properly displayed in the bounds of the container and not have any extra processing applied to it for different content scales.
The bug is best demonstrated visually:
glide-bug.webm
It is possible to interpolate ContentScale as described in this blog post with the following code:
Glide compose version used:
1.0.0-beta01
.In
GlideImage
, the implementation ofContentScale
is with acontentScaleTransform
.This causes a few issues:
Ideally the application of a content scale should not require the creation of separate images. The same image should be properly displayed in the bounds of the container and not have any extra processing applied to it for different content scales.
The bug is best demonstrated visually:
glide-bug.webm
It is possible to interpolate
ContentScale
as described in this blog post with the following code:In a comparison with Coil and a manual painter, Glide is unable to actually apply this interpolation. Consider the following:
Where
ImageComparison
is:The text was updated successfully, but these errors were encountered: