From: Vojtech Pavlik <vojtech@suse.cz>
To: David Ford <david+challenge-response@blue-labs.org>
Cc: "Ian E. Morgan" <imorgan@webcon.ca>,
Dmitry Torokhov <dtor_core@ameritech.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ALPS tapping disabled. WHY?
Date: Tue, 1 Mar 2005 12:54:32 +0100 [thread overview]
Message-ID: <20050301115432.GA5598@ucw.cz> (raw)
In-Reply-To: <422454A5.7070206@blue-labs.org>
On Tue, Mar 01, 2005 at 06:40:21AM -0500, David Ford wrote:
> I would also appreciate the return of good resolution. Blocky mouse
> startup moves make graphic editing rather difficult. No mouse movement
> until I have moved my finger a significant distance then the mouse all
> of a sudden jumps a dozen pixels before it "smoothly" glides along.
>
> I would also love to see the sync issues go away. :/ Whatever this
> patch(es) was supposed to accomplish, it introduced some rather
> undesirable side effects. a) sync issues, b) tapping, c) fine grain
> movements, d) loss of scroll sliding as well (moving your finger along
> the side/bottom of the glidepoint).
>
> Not griping, just providing feedback.
Can you check with a current -mm kernel whether any of the issues is
still there? Everything seems to work smoothly with my ALPS.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-03-01 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:29 ALPS tapping disabled. WHY? Ian E. Morgan
2005-02-25 3:08 ` Dmitry Torokhov
2005-02-27 7:50 ` Vojtech Pavlik
2005-02-28 22:23 ` Ian E. Morgan
2005-03-01 11:40 ` David Ford
2005-03-01 11:54 ` Vojtech Pavlik [this message]
2005-03-04 21:02 ` New ALPS code in -mm Benoit Boissinot
2005-03-04 21:13 ` Vojtech Pavlik
2005-03-07 7:14 ` Daniel Barkalow
2005-03-07 7:30 ` Vojtech Pavlik
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=20050301115432.GA5598@ucw.cz \
--to=vojtech@suse.cz \
--cc=david+challenge-response@blue-labs.org \
--cc=dtor_core@ameritech.net \
--cc=imorgan@webcon.ca \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox