🚀 go-pugleaf

Looks like I missed the boat on this one, but why not create a textfield where
an invalid value CANNOT be entered?  Just write your own textfield subclass and
ensure any invalid keystrokes are ignored.

Jason Burton wrote:

> > If you get a focus lost event, note that you *ALREADY* lost focus.  Focus
> > is *GONE*.  Another component *ALREADY* has the focus.  To move focus
> > back, the new component gets a focus lost event.  Will you then validate
> > the new component as well losing focus back to the original?
> > See how complicated all this is?  I personally highly advise *AGAINST*
> > doing things on a focus lost.  One good way to do validation is on each
> > keystroke by writing your own Document.  It's quite easy.
>
> A simple "user changed field" flag can be used to determine whether or not
> to perform validation.  This will prevent validation from occuring in the
> newly focused field when it is determined that the input in the last field
> is invalid.  Validating on key strokes can be a bad choice for things like
> database lookups based on current field value.
>
> Jason Burton