From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d0de2cc1a6ed8aaf1f4357180ead173b@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
From: Gorka Guardiola <paurea@lsub.org>
Date: Fri, 14 Jan 2005 15:59:48 +0100
In-Reply-To: <bc8c04c8073ac83c7cb40d6aa3926bb5@vitanuova.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 307dc4c0-eace-11e9-9e20-41e7f4b1d025

> paurea:

> 
> speaking of which, structuring it as a separate module means that the
> cooked events can become considerably more self explanatory, rather
> than trying to squeeze everything into bitfields in a structure that
> wasn't really designed for it.  for instance:
> 
> 	struct Cookedmouse {
> 		int buttons;
> 		int event;		# MCLICK, MSELECT, MCHORD, MEND
> 		int clickcount;
> 		Point xy;
> 		ulong msec;
> 	};

We will have to rewrite the state to make it per-mousectl in order to
make multiple mouses possible (ouch!!), so we will consider all this.

Is there anything you didn't understand or you found badly explained
in the documentation or is it just the squeezing of things in the struct
which you are compaining of?.

Thanks to all for your suggestions and commentaries.



								G.