From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] cooked mouse mode. From: Gorka Guardiola Date: Fri, 14 Jan 2005 15:28:04 +0100 In-Reply-To: <2902dc38936805d738ae00d8a6f9e799@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 3047caf0-eace-11e9-9e20-41e7f4b1d025 >> 2. you want to filter or transform a given raw mouse stream before cooking it > > it depends whether all transformations or filtering can > be expressed in your language. for instance, in the past i've > changed the x and y values in such a way that results of tests such > as ismove, or double-button clicks, would be different. > in some cases, i could do that after cooking i suppose, > but since that potentially introduces time delays (to check > for clicks/chording) i'm not sure i could as easily say > what my transformation actually did (as easily as for > raw point values) When you talk about the language you mean the implementation of cooked events or you mean the actual events generated?. The interpreter of events does not distinguish between X and Y movements, but it can be done easily if it is needed. G.