Re: [9fans] cooked mouse mode.

["Fco. J. Ballesteros" <nemo@lsub.org>]

Well, actually the plan was to get applications use the
cooked mode; and get rid of the need for raw mode.
Agree that some will have to use it, say, like you do in
the console with the keyboard, but that's not the common
case. That can probably explain why we wanted a mode change
and not a new channel with different semantics for mouse events.

But maybe I'm missing your point, am I?

>> You have to say
>> setmousemode(cooked),
>> and then no other thread has a way to get to
>> the raw mouse events.
> 
> except that a thread can read from the cooked mouse channel
> and *think* that it's reading raw events, with no way
> to tell.
> 
> if you're worried about it, you can just nil out the raw mouse
> channel in the Mousectl structure.