Mate you're a legend, they're both great ideas :) Just went with the
errorString for now, but next time (we're in a rush) I'll build an
AlwaysFailValidator or something and bind "enabled".

-J

On Sat, May 24, 2008 at 1:07 AM, Charlie Griefer <[EMAIL PROTECTED]>
wrote:

>   On Thu, May 22, 2008 at 11:12 PM, Josh McDonald <[EMAIL 
> PROTECTED]<dznuts%40gmail.com>>
> wrote:
> > Guys,
> >
> > Say I have a textInput, and I need to emulate the failure of a validator,
> > how do I go about it? I can't use the existing validator framework,
> because
> > the decision on whether or not that field is valid is based on a
> calculated
> > result rather than a simple validation of the textInput component itself.
>
> I believe you can use the textInput's errorString property. just set
> it to a (string) value. You may also still be able to use the
> existing validator framework. the validator has an 'enabled' property
> that you can toggle based on your calculated result.
>
> --
> A byte walks into a bar and orders a pint. Bartender asks him "What's
> wrong?" Byte says "Parity error." Bartender nods and says "Yeah, I
> thought you looked a bit off."
>  
>



-- 
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]

Reply via email to