🚀 go-pugleaf

In article <9480@milton.u.washington.edu> dlarson@blake.u.washington.edu (Dale Larson) writes:
>In article <635@incstar.uucp> lhotka@incstar.uucp (Glamdring) writes:
>>In article <1990Oct12.053232.22478@nas.nasa.gov>, 
>>         smithwik@pioneer.arc.nasa.gov (R. Michael Smithwick -- FSN) writes:
>>> So make sure to read the gadgets buffer and never assume the user hit the 
>>> CR.

Yes, this is safer.

>>My solution (this is the question part of this post...) is to always keep track
>>of which field was most recently activated (GADGETDOWN) and to perform the
>>field processing code on GADGETDOWN messages if the newly activated gadget
>>doesn't match the last activated gadget.  Is this the best way to do this?  It

Yeah, don't rely on the user doing anything that way you thought he
should do it.
  
>That looks like somewhat of an unnecessary pain.  If you have several string
>gadgets, hitting return in one of them should move you to the next.  There

Yes, ALSO. BUT you must not force the user to hit Return.
Look e.g. into preferences. Nearly every editor has also boolean gadgets
(just click) and string or numerical gadgets, too (type on the keyboard).
So it can easily happen that the user changes from gadget to gadget
simply by mouse clicking. This must not do harm to his inputs!

Like in street traffic, drive (and program) defensively, be aware
of ANY weird action the user might take.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk