Skip to content

Releases: luberda-molinet/FFImageLoading

FFImageLoading 2.2.24

07 Nov 20:40
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.23...v2.2.24

Xamarin.Forms - Important

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: #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.

Fixes

  • Xamarin.Forms: SetLoading never set to false when using fast renderer
  • Xamarin.Forms Android Fixed issues when using GestureRecognizers

FFImageLoading 2.2.23

04 Nov 11:55
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.22...v2.2.23

Xamarin.Forms - Important

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: #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.

New features

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.

Fixes

  • Android: Better animated gif detection (eg. photoshop generated gif files) - #777
  • iOS: Grayscale / Sepia transformations don't preserve transparency channel - #780
  • Android: Added more accurate delay for gif animation (more smooth animation)
  • Some enhancements to prevent linking
  • Various MSBuild / VS build issues fixes
  • Replace ToLower with ToLowerInvariant #792

FFImageLoading 2.2.22

26 Oct 14:34
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.21...v2.2.22

Xamarin.Forms - Important

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: #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.

Fixes

  • SVG gradient fills fix: #778

FFImageLoading 2.2.21

25 Oct 17:57
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.20...v2.2.21

Xamarin.Forms - Important

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: #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.

Improvements

  • Added Mock platform for unit testing in headless scenarios. You can enable it by setting: ImageService.EnableMockImageService = true
  • Added SvgCachedImage.Init() method (to avoid linking problems)
  • Code refactorings
  • Added FadeAnimationDuration / FadeAnimationForCachedImages for CachedImage views
  • SvgCachedImage improvements

Fixes

  • Android: exception while reading EXIF orientation shouldn't fail image loading
  • ManagedImageView (added lock when setting drawable because of exceptions when called multiple times at once)
  • Added missing PreserveAtrributes to prevent linking issues
  • Various Windows fixes
  • Fixed Windows MainThreadDispatcher regression which caused images to not appear
  • Fixes #763 SvgDataResolver not working when using in PCL project (missing constructor)
  • Fixed iOS webp regression
  • Added lock for SVG to PNG encoding (to avoid OOMs)
  • Windows Nuspec fixes / refactorings #762 #759 (Wrong dlls used on WinRT)
  • Xamarin.Forms.Windows: AsJPGStreamAsync doesn't ignore quality parameter
  • SVG fixes

FFImageLoading 2.2.20

04 Oct 11:39
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.19...v2.2.20

Xamarin.Forms - Important

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: #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.

Fixes

  • Fixed regression issue (NullReferenceException)

FFImageLoading 2.2.19

30 Sep 12:38
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.18...v2.2.19

Xamarin.Forms - Important

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: #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.

Fixes

  • UWP - fixed picking wrong display scale
  • Fixes #746 (Xamarin.Forms renderer crash)
  • SVG updates
  • MvxCachedImageView fixes
  • Fixes #536 - Android fade animation doesn't work when loading from cache and no placeholder is set

FFImageLoading 2.2.18

28 Sep 21:44
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.17...v2.2.18

Xamarin.Forms - Important

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: #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.

Fixes

  • More secure object disposing (always catching ObjectDisposedException when calling Dispose())
  • Dispose StreamRead in TaskParameter.Dispose method
  • Windows wrong colors in transformations fixes
  • Windows - fixes picking wrong display scale
  • Windows TintTransformation fixes
  • Xamarin.Forms ImageSourceBinding null exception fix

FFImageLoading 2.2.17

27 Sep 07:51
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.16...v2.2.17

Xamarin.Forms - Important

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: #545

Fixes

  • Xamarin.Forms Android renderer exception fix

FFImageLoading 2.2.16

26 Sep 16:33
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.15...v2.2.16

Xamarin.Forms - Important

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: #545

Fixes

  • Xamarin.Forms Windows fixes
  • Added MvxCachedImageView/MvxSvgCachedImageView for Windows (Preview)
  • Xamarin.Forms Android - fixed gesture recognizers not working on non-pre Xamarin.Forms versions (you can enable new (prerelease) behaviour with static CachedImage.FixedAndroidMotionEventHandler property

FFImageLoading 2.2.15

22 Sep 12:15
Compare
Choose a tag to compare

Complete history of changes available here: v2.2.14...v2.2.15

Xamarin.Forms - Important

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: #545

Fixes

  • Windows nuspec fixes