From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2aa227a62be6922f84c49173dd179b88@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] cooked mouse mode. From: Gorka Guardiola Date: Fri, 14 Jan 2005 15:24:58 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 302aad62-eace-11e9-9e20-41e7f4b1d025 >> 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. The language for cooked mouse is very general. Except for mouse gestures if you want them without any button clicked, I think most of the things you say can be used in cooked mode. You have Click preffix, Slide events and many others (look at the man page). > > 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. G.