On Sunday 30 January 2005 3:20 am, Peter Osterlund wrote:
> Dmitry Torokhov <[EMAIL PROTECTED]> writes:
> > On Tue, 25 Jan 2005 11:55:20 -0800, David Brownell <[EMAIL PROTECTED]>
> > wrote:
> > > The more serious one is that sometimes it seems to spontaneously emit
> > > click
> > > events while I'm moving finger across pad. Which means I've had to learn
> > > to
> > > plan my "mouse" motions to avoid areas where clicking could have bad
> > > effects.
> > > But that's not always possible ...
> >
> > That is default sensitivity not suiting your habits I think.
That answer isn't good. No defaults should be that dangerous!
But I suspect that's not really the issue...
> > I would
> > recomment trying out Synaptics X driver (which also does ALPS) so you
> > will be able adjust sensitivity the way you like it.
With the Synaptics X driver (as supplied by SuSE -- but NOT configured
automatically by the system install tool) and the ALPS parameters in the
README.alps from synaptics-0.14.0, and kernel parameters "usb-handoff"
and "mousedev.tap_time=0", I'm getting somewhat better results in this
particular area.
I see some new "mouse"-specific failure modes though:
(a) Sometimes tapping automagically generates extra clicks. For
example, pressing the delete button once will delete two or more
mail messages. Unfortunately it's not actually smart enough to
only kick in for spam! (I think this is exclusively when using
the touchpad itself.)
(b) Sometimes tapping the left button seems to start half a drag event.
For example a GUI button's menu pops up rather than performing the
action associated with the button. That could be some funky UI
settings, but it's not consistent ... and I've observed this with
very quick button presses. So I think something else is afoot.
(c) Sometimes tapping seems to only generate a "down" event ... until
I move the cursor, the "up" doesn't happen. Again, this is with
the left button, not the touchpad itself.
I haven't recently seen that nasty "motion emits random mouseclicks"
behavior, but given the way the hardware programs/trains user behavior,
it's hard to say for sure quite yet.
I've not done enough with non-GUI keyboard interactions to say if that
nasty keyboard blockage issue is gone or not; I wouldn't have seen it.
> I think the problem is that the tap detection in mousedev.c is very
> simplistic. It always generates a button click if the time between
> "finger down" and "finger up" is small enough, even if the finger was
> moved a large x/y distance. The X driver handles this with another
> parameter that specifies the maximum allowed distance. If the finger
> moved more than this distance, no button event is generated.
Sounds like "dueling heuristics" here!
I think the behavior I'm now seeing supports that hypothesis. But
it's hard to say without knowing more about how all the pieces fit
together.
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
