Access to Buttons in WizardContainer would be useful about cjwizard HOT 4 CLOSED

I think that it is also necessary (in my case to change their text). But how you will use it?

As the buttons are in the WizardContainer but normally you will need to change them inside the WizardPage or the PageFactory, how would you access it?

Also, as buttons are ruled by actions, maybe be better to get access to the action instead of the button itself.

from cjwizard.

Ah, this could also be used to work around #7 -- by disabling the Next button.

Exposing the Actions seems reasonable to me.

from cjwizard.

I think that this must be separated from access to buttons. What I think is we need a system to prevent the next to success more or less automatically and separated from access to buttons.

So you get:

• An event driven that is called when next is begin to occur. A simply and integrated way to tell that the wizard don't must change the page (and a way for you to change text or show messages with the problems).
• Access to buttons directly to modify them (for example for text, enable/disable, or whatever advance thing you need).

But is also recommended to have both, so in the event of "check before next" you can disable the buttons. For example:

1. A page with loguing credentials. You don't know if they are correct until you try.
2. The user fill the inputs and press Next.
3. "Check before next" is called and you check if they are correct.
4. They aren't so you change a label to tell the problem to the user and disable the Next button until it change the user or the password.

from cjwizard.

Closed because no updates on this issue since 2014. Please reopen if necessary.

from cjwizard.