From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Thu, 13 Jan 2005 20:59:06 +0000 [thread overview]
Message-ID: <666eb841359a58c552d3281e4f8041ba@vitanuova.com> (raw)
In-Reply-To: <da1382573dc026c06b1c8e78d5fb6e88@plan9.escet.urjc.es>
> 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.
next prev parent reply other threads:[~2005-01-13 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:30 Gorka Guardiola
2005-01-13 20:59 ` rog [this message]
2005-01-14 1:06 ` Gorka Guardiola Múzquiz
2005-01-14 13:57 ` rog
2005-01-14 13:54 ` Fco. J. Ballesteros
2005-01-14 14:05 ` rog
2005-01-14 14:02 ` Fco. J. Ballesteros
2005-01-14 14:26 ` rog
2005-01-14 14:24 ` Gorka Guardiola
2005-01-14 14:58 ` rog
2005-01-14 14:57 ` Fco. J. Ballesteros
2005-01-14 14:59 ` Gorka Guardiola
2005-01-14 15:09 ` rog
2005-01-14 15:06 ` Gorka Guardiola
2005-01-14 16:43 ` Rob Pike
2005-01-14 13:57 ` Gorka Guardiola
2005-01-14 14:18 ` Charles Forsyth
2005-01-14 14:06 ` Fco. J. Ballesteros
2005-01-14 14:12 ` Gorka Guardiola
2005-01-14 14:13 ` Gorka Guardiola
2005-01-14 14:15 ` Gorka Guardiola
2005-01-14 14:26 ` Charles Forsyth
2005-01-14 14:15 ` Fco. J. Ballesteros
2005-01-14 14:17 ` Gorka Guardiola
2005-01-14 14:24 ` Fco. J. Ballesteros
2005-01-14 14:38 ` Charles Forsyth
2005-01-14 14:28 ` Gorka Guardiola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=666eb841359a58c552d3281e4f8041ba@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).