-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why not use overlay for flushbar #54
Comments
Hi @huzhiren I don't know if you are already using it but Flushbar returns a Future that completes when it is fully dismissed. It can help you in the example you gave me. |
See issue |
After testing it, I have discarded using Overlay widget. The overlay does not stay on the screen once the route gets popped so it brings no benefit once the back button is pressed. |
+1 to this issue , it would be great if Flushbar allow us using |
Yes, a use case for you, because I'm thinking about how to solve this just now. :-) The user does some operation that is confirmed with a Flushbar. While the Flushbar is still visible, the user swipes open the
as usual, to dismiss the open drawer before starting its own work. However, as the Fushbar is still visible on screen, this pop doesn't work, the drawer isn't dismissed. A workaround would be, of course, to have a static function, something like |
Just for reference, this is how I solved it. Create your own file with appropriate helper routines:
and call |
It is fantastic to have flushbar, but it really mangles with the route state if you need to show flushbar at the same time you want to pop back to another page, which can also happen when user tap the back button on the phone.
The text was updated successfully, but these errors were encountered: