Now onConfirmBtnTap, onCancelBtnTap callback functions will return current context

[abhay-s-rawat]

Solved problem where when writing custom onConfirmBtnTap , popping the alert causes the screen to pop as we are popping top level context.

// In below example the alert stays on screen in macos as the we are popping the top level context. Popping it causes current screen to pop.
QuickAlert.show(
              context: context,
              type: QuickAlertType.error,
              title: "Deny rewards ?",
              cancelBtnText: 'Back',
              showCancelBtn: true,
              showConfirmBtn: true,
              //autoCloseDuration: const Duration(seconds: 10),
              onConfirmBtnTap: () {
// Some custom code
                Navigator.pop(context);
              },
            )

//Solution
// With below code we can catch the result too, thus detecting wheather the closure of alert is done by cancel/ok button or barrier dissmissable.
var result = await QuickAlert.show(
              context: context,
              type: QuickAlertType.error,
              title: "Deny rewards ?",
              cancelBtnText: 'Back',
              showCancelBtn: true,
              showConfirmBtn: true,
              //autoCloseDuration: const Duration(seconds: 10),
              onConfirmBtnTap: (ctx) {
// Some custom code
                Navigator.pop(ctx, true);
              },
            )

[abhay-s-rawat]

Any idea when publisher will push this to pub dev ?

[abhay-s-rawat]

Any update on this ?

[abhay-s-rawat]

Any update on this ?

[abhay-s-rawat]

??

[ItsAkashS22]

Hello @abhay-s-rawat

No need to take context into the function as a parameter, we can directly address/use the context of the parent.

Happy Coding!!!

[abhay-s-rawat]

If you try to pop eith parent context the current page gets popped not the dialog. I tested same in macos.