From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Fri, 14 Jan 2005 15:57:13 +0100 [thread overview]
Message-ID: <141f1f9a7cee225745d3eb7fb3ec3e67@plan9.escet.urjc.es> (raw)
In-Reply-To: <bc8c04c8073ac83c7cb40d6aa3926bb5@vitanuova.com>
[-- Attachment #1: Type: text/plain, Size: 75 bytes --]
Ok, your last argument convinced me.
I now agree with you. Thanks a lot.
[-- Attachment #2: Type: message/rfc822, Size: 3760 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
Date: Fri, 14 Jan 2005 14:58:46 0000
Message-ID: <bc8c04c8073ac83c7cb40d6aa3926bb5@vitanuova.com>
paurea:
> > 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.
i'd prefer to do it with a 10 line function (overhead almost zero)
than a 150 line separate filesystem implementation; especially as i might
wish to have my filtering affected by other stuff happing in my program.
nemo:
> But in any case, I dont' think it's good to let different apps use
> different kinds of mouse actions. That may lead to non-uniform UIs,
> which are not convenient for the user.
unfortunately modularity implies freedom and in this case the freedom
to build non-uniform UIs. i guess that's just the plan 9 way - it
hasn't got a standardised UI and probably never will. no standard
"widget set". no standard set of mouse actions.
it is, however, much simpler as a result.
the most you can do IMHO is to provide the tools to make it easy to
build uniform UIs (control(2) is an example) - to which end the new
mouse filtering is a nice contribution. i will certainly use it the
next time i have to write a plan 9 gui app, assuming i can understand
the documentation...
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;
};
next prev parent reply other threads:[~2005-01-14 14:57 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 [this message]
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=141f1f9a7cee225745d3eb7fb3ec3e67@plan9.escet.urjc.es \
--to=nemo@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).