You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
There's really nothing you can do with them that you can't do more cleanly through the back stack. Generalized something like the following, make the sample app use it, and deprecate the Popups.
class BlenderScreen {
transient boolean blendingConfirmed;
}
class ReallyBlendScreen {
final BlenderScreen caller;
}
class BlenderScreenView {
BlenderScreen args = ...
@OnClick(R.id.cancel) void cancel() {
args.cancelConfirmed = false;
flow.goTo(new ConfirmationScreen(args));
}
}
class ReallyBlendScreenView {
BlenderScreen args = ...
@OnClick(R.id.confirm) void confirm() {
args.caller.cancelConfirmed = true;
flow.goBack();
}
}
The text was updated successfully, but these errors were encountered:
To clarify, I believe the cancel() method actually should be named showConfirmation() or such. It's the action that causes the confirmation to show, not any cancelation of the confirmation.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's really nothing you can do with them that you can't do more cleanly through the back stack. Generalized something like the following, make the sample app use it, and deprecate the Popups.
The text was updated successfully, but these errors were encountered: