NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/sys/next/programm/5347

Text File | 1992-07-29 | 1.8 KB | 40 lines

Newsgroups: comp.sys.next.programmer
Path: sparky!uunet!psinntp!afs!greg
From: [e-mail] (Gregory H. Anderson)
Subject: Re: Formcell behaviour
Message-ID: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail]
References: <[e-mail]>
Date: Tue, 28 Jul 1992 22:31:17 GMT
Lines: 28

In article <[e-mail]>
[e-mail] (Robert D. Nicholson) writes:
> A mouse click event in an entry starts text editing in that entry.  A
mouse click event outside the Form or a RETURN key event while editing an
entry causes the action of the entry to be sent to the target of the entry
if there is such an action; otherwise the action of the Form is sent to
the target of the Form.

Because this object is braindead.  8^)

Seriously, only an actual <CR> forces the action method. This is a Bad
Thing, because I have watched many users not bother to hit any field
movement key after t hey finish typing in a field. If the next thing they
hit is the Save button, the last field never gets a chance to validate.
IMHO, any inter-field movement should trigger the action method.

For what you want, the Matrix which contains the FormCells must have a
text delegate, and you must use the text delegate methods (textWillEnd:,
textDidGetKeys:, etc.) to validate as they type. Even with this procedure,
the delegate methods seem to jump off at different points depending on
whether the keyboard or the mouse was used to instigate the field
movement. Bottom line, the action method is not reliable.

--
Gregory H. Anderson          | "We're very tolerant around here,
Benevolent Dictator-for-Life |  being only amateurs ourselves."
Anderson Financial Systems   | - Tortoise (Godel, Escher, Bach)
[e-mail]  (Nextmail OK)  |