Path: utzoo!utgpu!water!watmath!watdragon!violet!gjditchfield
From: gjditchfield@violet.waterloo.edu (Glen Ditchfield)
Newsgroups: comp.sys.mac.hypercard
Subject: Message orders (was: "select" anomaly)
Message-ID: <8490@watdragon.waterloo.edu>
Date: 15 Sep 88 15:18:02 GMT
References: <68272@sun.uucp>
Sender: daemon@watdragon.waterloo.edu
Reply-To: gjditchfield@violet.waterloo.edu (Glen Ditchfield)
Distribution: comp
Organization: U. of Waterloo, Ontario
Lines: 17

In article <68272@sun.uucp> BELSLEY%BCVMS.BITNET@MITVMA.MIT.EDU writes:
>I have little hope this comment will produce any results, because these
>types of anomalous message behaviors have never been corrected in the
>various incarnations of HC.  For example:
>
>... HC still does not send a closeField message every time a field closes,
>only if its contents have been changed.

And here's a problem with openField/closeField interaction:  if you click
on the same field several times in a row, an openField message is sent for
every click, but no closeFields are sent, _even if typing occurs between
the clicks_.  This messed my scripts up when I needed to process the
initial and final values of a field.  Do these extra openFields have any
usefulness other than as substitute mouseUps?

Now, if we can get a third person to complain ... maybe Dan Allen will
think its a movement!