they will
always return
their current values.
--
View this message in context:
http://www.nabble.com/How-do-I-force-evaluate-in-a-Wizard-steps-condition-to-run--tf4545108.html#a12975317
Sent from the Wicket - User mailing list archive at Nabble.com
.
This step is always enabled. Then no matter step C should be enabled or not,
the user will always see
a Next button.
Another option is try enabling wantOnSelectionChangedNotifications() to
refresh the whole page.
--
View this message in context:
http://www.nabble.com/How-do-I-force-evaluate
You would probably have to subclass WizardModel, or come up with a new
IWizardModel implementation completely. The former will probably
suffice, unless some strategic methods are declared final.
lizz wrote:
I really dont want to add more steps that the ones I already have. for the
case
;
}
});
}
}
--
View this message in context:
http://www.nabble.com/How-do-I-force-evaluate-in-a-Wizard-steps-condition-to-run--tf4545108.html#a12991207
Sent from the Wicket - User mailing list archive at Nabble.com
to be called
again.
How do I do that?
--
View this message in context:
http://www.nabble.com/How-do-I-force-evaluate-in-a-Wizard-steps-condition-to-run--tf4545108.html#a12970094
Sent from the Wicket - User mailing list archive at Nabble.com
the evaluate method to be
called again.
How do I do that?
What do you mean? IConditions are evaluated dynamically. So they will always
return
their current values.
--
View this message in context:
http://www.nabble.com/How-do-I-force-evaluate-in-a-Wizard-steps-condition-to-run--tf4545108.html