ItemBuilderWiza rd Step0_ItemTitle and Step2_ItemDescr ipton contain two
TextBoxes and I've done some validation for those TextBoxes in an
SelectedIndexCh anged event handler that sets the
ItemBuilderWiza rd.ActiveStepIn dex to return to Step0_ItemTitle when a
validation rule is not met.
The SelectedIndexCh anged event is raised by a list control that is displayed
using client-side code. Generally, once the list control is displayed it can
be used to raise SelectedIndexCh anged --but-- once the validation code in
the event handler resets the ActiveStepIndex and the user enters text into a
TextBox to comply with the validation rule the user can bang on the list
control forever; the SelectedIndexCh anged event will no longer firing.
What should I start thinking about to test further or what might be
considered to ensure the list control can continue to be used in the same
occurrence of the page once it has already been used to reset the
ActiveStepIndex of the Wizard? This loss of control state has also probably
been found --and resolved-- by those who have used the MultiView control.
TextBoxes and I've done some validation for those TextBoxes in an
SelectedIndexCh anged event handler that sets the
ItemBuilderWiza rd.ActiveStepIn dex to return to Step0_ItemTitle when a
validation rule is not met.
The SelectedIndexCh anged event is raised by a list control that is displayed
using client-side code. Generally, once the list control is displayed it can
be used to raise SelectedIndexCh anged --but-- once the validation code in
the event handler resets the ActiveStepIndex and the user enters text into a
TextBox to comply with the validation rule the user can bang on the list
control forever; the SelectedIndexCh anged event will no longer firing.
What should I start thinking about to test further or what might be
considered to ensure the list control can continue to be used in the same
occurrence of the page once it has already been used to reset the
ActiveStepIndex of the Wizard? This loss of control state has also probably
been found --and resolved-- by those who have used the MultiView control.