Re: Why thread limitations on mouse reads?

Very good call.

  - a

Brian Alliet <[email protected]> writes:
> On Apr 10, 2004, at 3:17 AM, Adam Megacz wrote:
>
>> The real solution (which I haven't gotten around to implementing yet)
>> is to have Press1, Release1, Move, etc put an (x,y) mouse position
>> instead of 'true'.
>
> If we do that we can also avoid constantly flooding the queue with
> mousemove events. We could only have the platform class send mousemove
> events when a Move trap is set somewhere on the surface.
>
> -Brian
>
>
> _______________________________________________
> core mailing list
> [email protected]
> http://lists.xwt.org/listinfo/core
>

-- 
"It's lucky," he added, after a pause, "that there are such a lot of
islands in the world.  I almost envy you, Mr. Watson."

                                                   -- Mustapha Mond