Re: [9fans] cooked mouse mode.

[Gorka Guardiola <paurea@lsub.org>]

> 
> just IMHO, i'd say that having the same channel produce two different
> types of event is at least as open to confusion as having a new
> channel and ignoring the old one.
> 
> by setting cooked mode, you are essentially changing the type of the
> channel.  in the future you might wish cooked mode events to contain
> other fields (for instance a "click count" to cope with more than
> double mouse clicks), in which case your suggested interface would not
> be sufficient - you'd have to change the definition of the Mouse
> structure, which doesn't seem right.

> 
> i'm not objecting to putting the declarations in mouse.h in the
> slightest; just that i don't think it's necessary to alter the old
> interface.
> 
> doing it this way also opens the possibility of having various
> different kinds of mouse cookery without affecting the original
> interface or code in the slightest.


The set is more or less complete. There is already a click count in it
(see the MCHORDB macro). I don't think it can get much more complete than
it is now (though it may be shortsightedness on my part). Anyway, I don't think
you will want different ways of cooking the mouse for each application
more than a central one, because it can make things difficult to understand.
You can get lost asking how is this application cooking the mouse?

										G.