Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Dealing with lots of messages (and dealing _selectively_)
Message-ID: <22602@ucbvax.BERKELEY.EDU>
Date: 16 Jan 88 03:49:00 GMT
References: <4346@garfield.UUCP> <3094@cbmvax.UUCP> <1983@amiga.amiga.UUCP> <525@nuchat.UUCP> <4376@garfield.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 41

In article <> somebody (lost to the winds of history) wrote:
>>
>>[Description of new flag added to Intuition]
>>
>>Your idea, I'm sorry to say, is a kludge.
>>
>>BUT, while we're talking about enhancements for 1.4(?), how about just making
>>MOUSEMOVE work like INTUITICKS... [Ie: don't send another until the first
>>is replied]

Bad for this reason:

You get sent the message and take a long time replying to it.  Now you
have a very old mouse message, but all the mouse moves since it have been
discarded.

I think jimm's new flag is just right.  IF you are only interested in
the LASTEST position of the mouse, just look.  The signal wakes you
up to the fact that the mouse moved.  Compare X,Y.  Perfect.

Before jimm suggested this, my idea was a counter:  "If XX mouse
messages queue up, then stop sending new ones.  At that point just
update the latest message with the new position.".

So a drawing program would trace a smooth curve until it gets too far behind.
Then it would jump ahead.  If you like things the old way, set the
counter to something very high (Say, 200).


>I would recommend that anyone
>writing intui-message controlled programs test out all sorts of weird
>combinations (like activating your window with right button down so you
>get a MENUUP before MENUDOWN)...

Good software practice.  Software should handle such events with grace.


|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (or try "cogsci")
 (")
  U	"Your theory is crazy... but not crazy enought to be true." -Niels Bohr