From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <c8a0cec407b68c490a17f87a1e0bc145@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cooked mouse mode.
From: "Fco. J. Ballesteros" <nemo@lsub.org>
Date: Fri, 14 Jan 2005 15:24:13 +0100
In-Reply-To: <341409a31670030ed4c2d4066c24846a@plan9.escet.urjc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 2fb7a038-eace-11e9-9e20-41e7f4b1d025

> I have just seen it. The state of the interpreter should be per mousectl. There is a global
> state which shouldn't be there in order to be able to cope with more than one mouse.

Arggh!

I always thought the state was kept along with mousectl. I
agree that it's not a good way to do it if we keep goblal state.

We'll fix it, perhaps by using a different channel, as some of
you have suggested.

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.

thanks for your help