Image loading, caching & transforming library for Xamarin and Windows
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.23...v2.2.24
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Xamarin.Forms (Android) now uses fast renderers by default if possible (correct XF version). You can enable / disable fast renderers by CachedImageRenderer.Init(enableFastRenderer: [true/false]
override.
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.22...v2.2.23
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Xamarin.Forms (Android) now uses fast renderers by default if possible (correct XF version). You can enable / disable fast renderers by CachedImageRenderer.Init(enableFastRenderer: [true/false]
override.
ToLower
with ToLowerInvariant
#792Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.21...v2.2.22
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.20...v2.2.21
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
ImageService.EnableMockImageService = true
SvgCachedImage.Init()
method (to avoid linking problems)FadeAnimationDuration
/ FadeAnimationForCachedImages
for CachedImage viewsPreserveAtrributes
to prevent linking issuesMainThreadDispatcher
regression which caused images to not appearSvgDataResolver
not working when using in PCL project (missing constructor)AsJPGStreamAsync
doesn't ignore quality parameterComplete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.19...v2.2.20
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
NullReferenceException
)Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.18...v2.2.19
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.17...v2.2.18
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true
if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
ObjectDisposedException
when calling Dispose()
)Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.16...v2.2.17
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.15...v2.2.16
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
MvxCachedImageView/MvxSvgCachedImageView
for Windows (Preview)CachedImage.FixedAndroidMotionEventHandler
propertyComplete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.14...v2.2.15
FFImageLoading has a regression since 2.2.4 which caused CachedImage
to always to fill entire space available (different behaviour than Image
. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545