Path: utzoo!mnetor!uunet!husc6!hao!ames!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga
Subject: Re: Dealing with lots of messages
Message-ID: <1983@amiga.amiga.UUCP>
Date: 7 Jan 88 03:22:00 GMT
References: <4346@garfield.UUCP> <3094@cbmvax.UUCP>
Reply-To: jimm@amiga.UUCP (Jim Mackraz)
Distribution: na
Organization: Commodore-Amiga Inc., 16795 Lark Ave. Suite 106, Los Gatos CA 95030
Lines: 29
Keywords: messages IDCMP MOUSEMOVE

In article <3094@cbmvax.UUCP> steveb@cbmvax.UUCP (Steve Beats) writes:
>In article <4346@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
>> [ good idea number 1 ] -John

> [ interesting idea number 2 ] -Steve

These are both OK.  I am proposing that in next release (V1.4?),
a flag be added to the Window named SIGNALMOUSE.  When set, if
you are to be sent a mouse movement message, it won't be sent. 
Rather your Window->UserPort will be signalled.  You'll wake up,
GetMsg() NULL, and then just check Window->MouseX/Y or
PropInfo->Horiz/VertPot, or whatever, in a kind of prodded polling
fashion.

No backlog, unsightly comparisons, distasteful state toggling.

Religious leaders might not like some of the synchronicity implications
of this, but it will serve lots of uses.  Note that mouse clicks and
other discrete events are still to be used with the X/Y position
synchonously associated with them in the message.

Great idea.  Think I'll put it in.  Oh, look, it's done.   ;&)
	jimm

-- 
	Jim Mackraz, I and I Computing	  
	amiga!jimm	BIX:jmackraz
Opinions are my own.  Comments regarding the Amiga operating system, and
all others, are NOT to be taken as Commodore official policy.