From: Gorka Guardiola <paurea@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Fri, 14 Jan 2005 15:24:58 +0100 [thread overview]
Message-ID: <2aa227a62be6922f84c49173dd179b88@plan9.escet.urjc.es> (raw)
In-Reply-To: <d3de444e0a2b0cd175eb4d03bdbf2eae@vitanuova.com>
>> Well, actually the plan was to get applications use the
>> cooked mode; and get rid of the need for raw mode.
>
> the nice thing about raw mode is that the relationship with what the
> mouse is actually doing is beautifully simple and easy to explain.
>
> "cooking" the mouse involves the application of a certain amount of
> convention as to what sort of events one would like to see.
>
> your convention assumes that applications are interested in clicking
> and chording.
>
> some applications might wish to know about other kinds of mouse
> action, mouse gestures, or click-and-hold, perhaps.
The language for cooked mouse is very general. Except for mouse gestures
if you want them without any button clicked, I think most of the things you
say can be used in cooked mode.
You have Click preffix, Slide events and many others (look at the
man page).
>
> or, as charles points out, one might wish to pre-filter events, for
> example to remove redundant mouse-moved events or perhaps to integrate
> input from another device.
I would guess that kind of thing should be done with a filesystem wrapper like
we are already doing.
G.
next prev parent reply other threads:[~2005-01-14 14:24 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 [this message]
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=2aa227a62be6922f84c49173dd179b88@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).