From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <666eb841359a58c552d3281e4f8041ba@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Thu, 13 Jan 2005 20:59:06 +0000
From: rog@vitanuova.com
In-Reply-To: <da1382573dc026c06b1c8e78d5fb6e88@plan9.escet.urjc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 2ed0b556-eace-11e9-9e20-41e7f4b1d025

> We have written and submitted a cooked-mouse mode patch. 
[...]
> A typical use for this would be:
> 
> 1) call setmousemode
> 
> setmousemode(mousectl, MCOOKED);

is there a particular reason why this has to be a patch in mouse(2)?
could it not be implemented simply by a simple thread that receives
events from the usual mouse channel, translates to "cooked" mouse messages
and sends these down another channel, to be received by the application?

say:
	Channel *cookedmouse(Channel *);

that way none of the existing code needs to change; it seems to me
that this is the kind of thing that the channel idiom is tailor-made
for.

i'm probably missing something.