Why would tab justify a separate event?
If to reflect updated edit value elsewhere
on the form, then why not account for a different
way to move away from a control by mouse click
for example?
So maybe these two events from isigraph would make
more sense to reflect control update?
focus focus gained
focuslost focus lost
Speaking of tab as a key, it might not be very
interesting exclusively, but a general event
for chars would take care of this and other cases:
char key press
Either focus lost or char allow validation,
that will signal any errors in the format.
--- Tracy Harms <[EMAIL PROTECTED]> wrote:
>
> I am interested in learning why the decision was made to have tab not
> count as an interface event. I'm also curious to understand at what
> level the decision (or necessity) occurred, as clearly this has nothing
> to do with the core of the language.
>
> T. H.
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
