home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!psinntp!afs!greg
- From: greg@afs.com (Gregory H. Anderson)
- Subject: Re: Formcell behaviour
- Message-ID: <1992Jul28.222721.422@afs.com>
- Sender: greg@afs.com
- Reply-To: greg@afs.com
- References: <1992Jul27.132231.19873@monu6.cc.monash.edu.au>
- Date: Tue, 28 Jul 1992 22:27:21 GMT
- Lines: 28
-
- In article <1992Jul27.132231.19873@monu6.cc.monash.edu.au>
- ede978e@monu6.cc.monash.edu.au (Robert D. Nicholson) writes:
- > I have a form and one of the formCells connected to a validateField
- method. I have a number of buttons which are enabled only if the fields
- are valid. When I type in the formcell (not pressing return) or click
- into another cell or even _OUTSIDE_ the form the action is not sent.
- WHY!!!!!.
- >
- 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)
- greg@afs.com (Nextmail OK) |
-