From: Gorka Guardiola <paurea@lsub.org>
To: 9fans@cse.psu.edu
Subject: [9fans] cooked mouse mode.
Date: Thu, 13 Jan 2005 17:30:45 +0100 [thread overview]
Message-ID: <da1382573dc026c06b1c8e78d5fb6e88@plan9.escet.urjc.es> (raw)
We have written and submitted a cooked-mouse mode patch.
It means that while using mouse(2), setmousemode
can be called in order to stop getting raw mouse events and start getting them
cooked so the state machine for proccessing single clicks, double clicks, slides,
chords and so on (which is difficult to get right) isn't rewritten
for every application and has a clear boundary. The state machine is implemented
as an interpreter for a minilanguage with the program hardcoded in it, but all
that is isolated from the user of the library. A typical use for this would be:
1) call setmousemode
setmousemode(mousectl, MCOOKED);
2) receive events from the channel already processed:
for (;;) {
switch(alt(alts)) {
case Akeyboard:
if(r==DELETEKEY)
threadexitsall(nil);
break;
case Areshape:
resized(1);
break;
case Amouse:
if (button==(MCLICK|MEND|2)){
//single click with the 2 button
}
if (button==(MCLICK||MDOUBLE|MEND|1)) {
//double click with the 1 button
}
if ((button&(MFLAGS|7)) == (MEND|MCHORD|MCLICK|4|1)){
if (MCHORDB(m->buttons,0) == 1){
//chord with buttons 1 and 3, the first being 1.
}
}
}
}
We are finding it very useful in Plan B. Oppinions, ideas, suggestions?.
The genealogy of this is funny:
squeak (language for the mouse) ->aleph->libthread->cooked mouse
G.
next reply other threads:[~2005-01-13 16:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:30 Gorka Guardiola [this message]
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
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=da1382573dc026c06b1c8e78d5fb6e88@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).