progress_loader_overlay 4.0.0 progress_loader_overlay: ^4.0.0 copied to clipboard
A flutter package to show an easy to use and fully customizable progress loader as an overlay.
[4.0.0] - 2024-06-03 #
- Added
onStatusChangedStream
, which can be listened to to know when the Progress Loader starts showing or dismissing. - Added
PopScopeLoader
to replace the deprecatedWillPopScopeLoader
.PopScopeLoader
is the equivalent to Flutter'sPopScope
but adds extra control for the Progress Loader. - Deprecated
WillPopScopeLoader
, following Flutter's deprecation ofWillPopScope
. - Breaking (iOS only): This is unlikely to break anyone's code but the default Progress Loader was
changed on iOS only to allow the swipe back navigation gesture to work with
PopScopeLoader
. - Example app: Updated to use
PopScopeLoader
instead ofWillPopScopeLoader
. - Example app: Updated Android Gradle dependencies.
[3.0.3] - 2023-06-02 #
- Updated for Flutter 3.10 and Dart 3.
- Update License wording (same license).
- Updated README to add shields.
[3.0.2] - 2022-07-18 #
- Fixed
SchedulerBinding
warnings. - Example app: Migrated to Android embedding v2. Updated Android dependencies.
- Reorganized CHANGELOG.md to have entries ordered from newest to oldest.
[3.0.1] - 2021-05-25 #
- Fixed a bug causing the loader to not dismiss in some cases because of ProgressLoaderWidgetController.dismiss() future not completing in the default loader.
- Added an extension method in example code to show an nice way of handling FutureTicker.
- If you are using ProgressLoaderWidgetController in your code and awaiting an AnimationController.dismiss() to call ProgressLoaderWidgetController.dismiss() then check the updated example code to avoid making the same mistake as I did.
[3.0.0] - 2021-05-24 #
- [BREAKING]
- Fixed a bug causing the loader to not show if show was called before the previous loader was done dismissing.
- Refactored example code, and added a test page to visually test sync issues like the one stated above.
- This is probably not breaking anyone's code but could potentially do, so marking this as a breaking change.
[2.0.0] - 2021-05-15 #
- [BREAKING] - Migrated to null-safety.
[1.0.0] - 2020-11-05 #
- Initial release.