Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!kksys!orbit!incstar!lhotka
From: lhotka@incstar.uucp (Glamdring)
Newsgroups: comp.sys.amiga.tech
Subject: Re: GUI Style Question
Message-ID: <907@incstar.uucp>
Date: 1 Nov 90 00:23:08 GMT
References: <1990Oct25.212714.26909@unislc.uucp> <10109@milton.u.washington.edu> <6919@sugar.hackercorp.com> <10177@milton.u.washington.edu> <6927@sugar.hackercorp.com>
Organization: INCSTAR Corp, Stillwater MN
Lines: 23

In article <6927@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
> In article <10177@milton.u.washington.edu> dlarson@blake.u.washington.edu (Dale Larson) writes:
>> Programs which aren't picky enough in realtime are annoying, too.  If the 
>> validity of several fields can be checked with help from an earlier field,
>> such checking should be done early to save entry of several bogus fields.  
> 
> Great, now what happens when you decide to go back to the previous fields
> to change it to make the next field valid? I don't know how many times I've
>  [counter woes deleted...]
> 

I didn't mean to imply in my earlier posting that you would be prevented from
returning to earlier fields (via the mouse of course... yet another complaint
that you can't trap the up arrow in a string gadget...) to change their values. 
On the other hand, that earlier field will have to be processed as soon as you
enter the data into it, or the condition you are trying to fix won't be
fixed...
 ______________________________________________________________________
/ Rockford Lhotka				INCSTAR Corp	       \
| Systems Administrator				PO Box 285	       |
| incstar!lhotka@uunet.uu.net         		1990 Industrial Blvd   |
\ 612/779-1701					Stillwater, MN 55082   /
 ----------------------------------------------------------------------