Hi Matt,
MC> Hope this clarifies things,
yes, it sure does! Thanks for that! Let me just comment on you,
because I couldn't fully agree with you ;)
Let's imagine a form in the context of the order processing of a
shopping cart. When the user follows the process, why should he leave
a certain field open to fill in later? I don't see a use for that. For
me, one big advantage of the Flex validation would be that if I tab
out of an empty required field I instantly will receive an error
message. I'm sure that there is a way to trigger the validation of the
certain field capturing the key event or whatever in AS, but I would
really like to be able to choose how my validation should behave.
There might be situations where the application should behave like you
described, I don't know. But in my sense of understanding validation
it means that a required field is required - always and not just if I
entered something before.
Otherwise - let's say my form is completly empty at the start - I
could tab throught an n-fielded form and pushing my "action"-button
and will receive my validation result during click time. For me that's
not the "natural" behaviour, it's very similar to HTML forms with some
JavaScript which checks for errors after collecting all that data -
which I always disliked ;)
Cheers
Kai
MC> It is intended behavior that if you do not
MC> change anything in an initially blank field the validator will not fire.�
The
MC> reason we did this is that many times a user will tab through a field
intending
MC> to fill it in later, so we found it to be frustrating when the field
MC> immediately turned red ("how can my value be invalid when I didn't
MC> enter anything yet?").� Additionally, if you had an alert or some other
obtrusive
MC> mechanism to indicate that validation had failed it was even more
frustrating
MC> to the user.� So we decided if they didn't actually change the value and
MC> the value had not been set before, don't fire validation.� Essentially
MC> you have to get one real value (not null, not undefined, not empty string)
before
MC> binding and validation will start to fire.
