Aspire S7 touchpad parses short moves as clicks when tap-to-click enabled

thirtyandseven

Just got my new Aspire S7 in the mail yesterday, and the touchpad is driving me absolutely insane.  When I make quick, short movements (say, moving the cursor 15 pixels or less on the screen), the cursor moves initially, but then changes its mind, jumps back to its original location, and clicks in that original location.

 

This occurs only when tap-to-click is enabled. The issue is not the sensitivity setting (I have tried every combination of sensitivity settings in the Synaptics driver and Windows interfaces).  Instead, the problem is the fact that the Synaptics touchpad drivers interpret small movements as clicks.  This should not be the case--if there is any cursor movement, I intend to move the cursor, not to click.  However, it occurs whether I use the driver that shipped with the laptop, either driver from the Acer site (Synaptics or Elon), or the newest driver from the Synaptics website.

 

Has anyone found a way to modify the driver to fix this glitch for Windows computers?

 

In linux, there is a variable that directly modifies the maximum amount of movement that will be interpreted as a click:

 

Option "MaxTapMove" "integer"
    Maximum movement of the finger for detecting a tap. Property: "Synaptics Tap Move" 

Additionally, there even appears to be a patch specifically for this issue in linux, as according to the developer, "the range that is considered moving during tapping is somewhat generous in the default settings."

 

Synaptics itself states that "to detect a tapping gesture, the TouchPad looks for Z to increase beyond the touch threshold and then to return to nearly zero after only a fraction of a second, with little or no X or Y motion during this time."  Apparently, the default tolerance for a "little" X or Y motion on the touchpad is too high.

 

How can I fix this in Windows?  TYIA.

Clyde

It seems that disabling tap to click would be the only way, unless you can find an updated driver.