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
Back button not disabling #1
Comments
After cloning the repository and debugging I'm seeing a pattern. with the following methods:
RuntimeWizardStrategy.SetButtonStates() I navigate to the page in question the following happens.
This essentially overwriting my change to the Back button's enabled property. |
Hi Ed, I use the wizard in work projects (have done for years) and haven't seen that issue though it's probably down to the fact that not so long ago I attempted to "clean" the code somewhat and probably introduced it (no tests!) whilst my projects still use the old version. Are you in a position to patch it and submit the change? I'm not going to get the chance to look at it this week at least due to "going live" on a project at work. Cheers, Steve |
Hi Steve, I've using the wizard right now on one of my projects, and I have the same issue Ed is having, but I'm facing this issue with both Back & Next buttons. Setting the button enable to false in the PageChanged event is overwritten by the SetButtonStats() method. Regards, |
After removing the enabling of the Next button in the SetButtonStats() at the middle page, it worked fine for me.
|
Having an odd issue where I am attempting to toggle the enabled state of the back button when pages are shown but it doesn't seem to work. The back button is always enabled. The next button toggles just fine though.
// This works
this.advancedWizardControl.NextButtonEnabled = false;
// This does nothing.
this.advancedWizardControl.BackButtonEnabled = false;
Clarification Edit:
When a given page is shown, I set the backButtonEnabled setting to false. I am attempting to disable the Back and/or Next button depending on what options the user has selected.
The text was updated successfully, but these errors were encountered: