Re: [9fans] cooked mouse mode.

[rog@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.

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.

it seems right to me that the mouse events arrive in
lowest-common-denominator form, and than can then be transformed by
the application into whatever form is most convenient for that
application.  (it's just a pity that the Channel* type in C can't be
parameterised with the type of the value it holds).

keeping the transformation function separate is more modular.  it's
just the kind of reason that the channel-based model was used, surely?