From: Gorka Guardiola <paurea@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Fri, 14 Jan 2005 15:59:48 +0100 [thread overview]
Message-ID: <d0de2cc1a6ed8aaf1f4357180ead173b@plan9.escet.urjc.es> (raw)
In-Reply-To: <bc8c04c8073ac83c7cb40d6aa3926bb5@vitanuova.com>
> 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.
next prev parent reply other threads:[~2005-01-14 14: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
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 [this message]
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=d0de2cc1a6ed8aaf1f4357180ead173b@plan9.escet.urjc.es \
--to=paurea@lsub.org \
--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).