Date: Sun, 6 Jun 2004 19:48:39 +0200
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/RFT] Metter mixing of relative & absolute devices by mousedev
Message-ID: <20040606174839.GB6561@ucw.cz>
References: <200405060144.52477.dtor_core@ameritech.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200405060144.52477.dtor_core@ameritech.net>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1266
Lines: 27

On Thu, May 06, 2004 at 01:44:52AM -0500, Dmitry Torokhov wrote:
> Hi,
> 
> Currently mousedev re-interprets every event for every client (reader) that
> has either /dev/input/mouseX or /dev/input/mice opened. For absolute events
> mousedev converts them into relative motion data using device's size, screen
> size and previous absolute position. For /dev/input/mice that gets events
> all devices this poses a small problem as true relative events do not adjust
> previous position - so if you were using touchscreen, then a mouse and were
> to touch the thouchscreen again the cursor would jump before getting to your
> finger. 
> 
> Please consider the following patch - it processes every event only once and
> converts it into relative motion. The mousedev clients are fed with relative
> motion data only this eliminating "jumping cursor" problem. 

I see I didn't comment on this one yet: Yes, it makes a lot of sense.
Can you prepare a pull for me, or do I have it already?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/