-
Notifications
You must be signed in to change notification settings - Fork 22
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
On back button pressed event #22
Comments
Hi Ahmed,
Could you please explain more about this use-case, inside which screen you mean? For closing the back buttons would work. Also are you flutter ios or android? |
Hi hi
I'd like to add some other widgets above or below the chatting widget, perhaps
Yes, it does work 100%. but I want to capture the closing event and do some logic like logging some event, redirecting, etc.
Android for now for getting it ready, but I want to have it working on both of them and published in my iOS version as I have iOS version published and working fine. |
Hi Ahmed, Adding our Android developer @reytum to update your usecase. |
@AhmedNourJamalElDin As of now we do not provide an option to add the chat screen inside your widget in Flutter. The chat screen will open independently. Also we do no provide an event for the back press of the chat button. One workaround you could use to achieve this is by checking the onResume and onPause events in your screen from where the chat screen is launched. So when the chat is opened, the event fired would be onPause and when you return back from the chat screen, onResume event will be fired. Hope this thread could be helpful: https://stackoverflow.com/questions/49869873/flutter-update-widgets-on-resume |
Thanks a lot. I will try them. |
Hi,
I wanted to show the chat as a widget inside a screen. but it seems not possible, right?
so I have changed my mind.
Now I want to know if the chat is closed by pressing the back button or via Android physical back button or anyway. just need to add some code at closing the chatting screen.
How to achieve so?
Thanks
The text was updated successfully, but these errors were encountered: