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
Calling WizardControl.NextPage(wizardPage, true) results in opening wizardPage,
but also in an inmediate continuation to the page following that in the WizardControl.Pages,
which may even cause the entire wizard to finish.
Strangely, this second next doesn't fire the Commit event.
But is does fire a second SelectedPageChanged.
This breaks my navigation.
I currently have no way of preventing it.
This is a try-out in which I have already put considerable effort.
This may be the breaking problem.
Please react to this issue.
The text was updated successfully, but these errors were encountered:
The way to interrupt this behaviour is to set WizardPageConfirmEventArgs.Cancel = true
in the Commit handler. Which makes sense, but is a matter of interprestation.
Calling WizardControl.NextPage(wizardPage, true) results in opening wizardPage,
but also in an inmediate continuation to the page following that in the WizardControl.Pages,
which may even cause the entire wizard to finish.
Strangely, this second next doesn't fire the Commit event.
But is does fire a second SelectedPageChanged.
This breaks my navigation.
I currently have no way of preventing it.
This is a try-out in which I have already put considerable effort.
This may be the breaking problem.
Please react to this issue.
The text was updated successfully, but these errors were encountered: