When a page pops, a dialog or bottomsheet cannot be closed automatically about one_context HOT 6 CLOSED

@muneeb-wecrunch @rishli @bitores
Hey guys, I'm going to work on this tomorrow, and try to release this update on weekend

from one_context.

Hi @bitores
If you need to close dialogBoxes you just need to call OneContext().popDialog()
If you need close dialogs when android button is pressed, please await for the next release, this feature will be delivered soon.

The dialogBoxes in this package is not intended to be closed automatically when a route pops(Android back pressed), the behavior expected is to close the dialogs(if visible) first and after that, close the page.

I hope I managed to answer you, if not, please, leave a comment. I would appreciate sugestions too.

from one_context.

Hi @bitores, please, can you check this branch if it works for your needs?

Configure the one_context package's dependency to the github in pubspec.yaml

  one_context:
    git:
      url: git://github.com/emanuel-braz/one_context.git
      ref: feature/android-backbutton

from one_context.

Hi @bitores, please, can you check this branch if it works for your needs?

Configure the one_context package's dependency to the github in pubspec.yaml

  one_context:
    git:
      url: git://github.com/emanuel-braz/one_context.git
      ref: feature/android-backbutton

Please release the official version, thank you.

from one_context.

@emanuel-braz still not fixed in the latest version.

from one_context.

Closing this issue with PR #15

Dialogs and Modal bottom sheets will be closed automatically with back button(android).

If you need close all dialogs, even if you do not know how many is open, you can call popAllDialogs() (for example before screen transition)

If you do not want dialogs get closed automatically, then use barrierDismissible or isDismissible == false, for Dialogs and ModalBottomSheet respectively.

Snackbars and BottomSheets keep opened, since they does not return a compatible "Future". Making changes on that, lead to cause break changes and actually I'm not sure if this behavior is appropriate for that components.

from one_context.