Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!decwrl!sun!pitstop!sundc!seismo!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Dealing with lots of messages
Message-ID: <1405@sugar.UUCP>
Date: 16 Jan 88 08:45:30 GMT
References: <8801130131.AA26382@cory.Berkeley.EDU>
Organization: Sugar Land UNIX - Houston, TX
Lines: 24

In article <8801130131.AA26382@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> >BUT, while we're talking about enhancements for 1.4(?), how about just making
> >MOUSEMOVE work like INTUITICKS... that is, you don't send a new MOUSEMOVE
> >message to a window until it's ReplyMsg-ed the previous one. Simple, clean,
> >consistant. What more can you want?

> 	Nahhh.  Sometimes you want the accuracy (say somebody is tracing
> a curve) even if the system is loaded.   When I want to handle mousemove at
> program speed rather than message port speed, I simply flag the move and the
> last coordinates and handle it after GetMsg() returns NULL... easy.

> 	Checkout the source to FILES on mod sources for an example.

Good point. OK then, how about this:

Add a new flag, but call it FASTMOUSE. FASTMOUSE would work like MOUSEMOVE
crossed with INTUITICKS. I avoid MOUSEMOVE these days because of all the
overhead.

I realise it should possibly be called SLOWMOUSE, but I want to retain
compatibility with COMPLEXREFRESH and STUPIDREFRESH windows :->.
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.