mactel-support team mailing list archive

[Jim Rorie <jimrorie@xxxxxxxxxxx>]

Public bug reported:

I've noticed erratic functioning of the macbook touchpad (5,1) with
regards to multi-touch.  When moving your index finger on the touchpad,
the mouse tracks fine until another finger comes within rage of the
touchpad to register.  This finger does NOT need to contact the pad and
generate a z value that exceeds fingerhigh.  It simply needs to be
identified.  The result is that the mouse will pause when the second
finger is seen, causing sticky mouse behavior.  This is a particular
problem with with my sensitive hardware as the touchpad will register a
z~=10 when a finger is within 3cm of touching.  Thus I have to keep my
others fingers way clear of the touchpad, which is hard to do
consistently.

I would expect the proper solution would be that all fingers must be z
>= fingerhigh to be acknowledged or a fingerhigh2 parameter needs to be
created in the policy file.  I would also expect this problem to exist
for 3,4,5 fingers, etc.

** Affects: mactel-support
     Importance: Undecided
         Status: New

-- 
FingerLow/FingerHigh values ignored for second finger on touchpad
https://bugs.launchpad.net/bugs/371260
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.

Status in Mactel Support: New

Bug description:
I've noticed erratic functioning of the macbook touchpad (5,1) with regards to multi-touch.  When moving your index finger on the touchpad, the mouse tracks fine until another finger comes within rage of the touchpad to register.  This finger does NOT need to contact the pad and generate a z value that exceeds fingerhigh.  It simply needs to be identified.  The result is that the mouse will pause when the second finger is seen, causing sticky mouse behavior.  This is a particular problem with with my sensitive hardware as the touchpad will register a z~=10 when a finger is within 3cm of touching.  Thus I have to keep my others fingers way clear of the touchpad, which is hard to do consistently. 

I would expect the proper solution would be that all fingers must be z >= fingerhigh to be acknowledged or a fingerhigh2 parameter needs to be created in the policy file.  I would also expect this problem to exist for 3,4,5 fingers, etc.