From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/RFT] Metter mixing of relative & absolute devices by mousedev
Date: Sun, 6 Jun 2004 13:48:57 -0500 [thread overview]
Message-ID: <200406061348.57160.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040606174839.GB6561@ucw.cz>
On Sunday 06 June 2004 12:48 pm, Vojtech Pavlik wrote:
> 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?
>
You should have pulled it last time (before today).
--
Dmitry
prev parent reply other threads:[~2004-06-06 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 6:44 [RFC/RFT] Metter mixing of relative & absolute devices by mousedev Dmitry Torokhov
2004-06-06 17:48 ` Vojtech Pavlik
2004-06-06 18:48 ` Dmitry Torokhov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406061348.57160.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.