Jim Hudson
2/14/2008 2:53:00 PM
Ahah!!! I thought about your suggestion, and tried a variation, and SOLVED
it!!
I should mention that I'm building my app with VS2008, and it's configured
to use .Net 3.5. The trick that I describe below may not work on .Net 3.0.
The trick is to set up the validation in XAML, as normal:
<TextBox x:Name="InputNameTextBox" >
<TextBox.Text>
<Binding Path="InputName" UpdateSourceTrigger="LostFocus">
<Binding.ValidationRules>
<NameValidationRule />
</Binding.ValidationRules>
</Binding>
</TextBox.Text>
</TextBox>
BUT, instead of hooking up a LostFocus handler in the XAML, I hook it up in
the code-behind:
InputNameTextBox.LostFocus += new
RoutedEventHandler(InputNameTextBox_LostFocus);
.
.
.
void InputNameTextBox_LostFocus(object sender, RoutedEventArgs e)
{
if (Validation.GetHasError(InputNameTextBox) ||
Validation.GetHasError(otherTextBox) ||
Validation.GetHasError(yetAnotherTextBox))
{
OKButton.IsEnabled = false;
CancelButton.IsDefault = true;
OKButton.IsDefault = false;
}
else
{
OKButton.IsEnabled = true;
CancelButton.IsDefault = false;
OKButton.IsDefault = true;
}
}
THEN, at runtime, the ValidationRule fires FIRST, FOLLOWED by the LostFocus
handler.
Thanks for your help!!
--
Jim Hudson