- Breaking:
ProgressLoader().show()
now takes an OverlayState rather than a BuildContext. This gives more flexibility to choose what context the overlay should use. For example you can now use the OverlayState of the Material App navigationKey, and avoid using the local context entirely. This is particularly useful if your context is being disposed before the overlay gets a chance to show.
- Fixed formatting.
- 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.
- Updated for Flutter 3.10 and Dart 3.
- Update License wording (same license).
- Updated README to add shields.
- Fixed
SchedulerBinding
warnings. - Example app: Migrated to Android embedding v2. Updated Android dependencies.
- Reorganized CHANGELOG.md to have entries ordered from newest to oldest.
- 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.
- [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.
- [BREAKING] - Migrated to null-safety.
- Initial release.