Turning off "accidental touchpad" feature?

Discussion in 'MacBook' started by bluesTank, Oct 27, 2008.

  1. bluesTank macrumors regular

    Oct 21, 2008
    Does anyone know if there is a way to turn off the feature where it negates any accidental touchpad movements? I heard that this was an option on earlier macbooks, but I can't seem to find it anywhere.

    My trackpad gets unresponsive at times, and I suspect this might be the cause. Especially along the borders of the trackpad...does anyone else have this issue?
  2. sirozha macrumors 6502a

    Jan 4, 2008
    I cannot find this feature either, and neither can I find any place where I can control trackpad sensitivity on the late 2008 Macbook.

    What I have noticed with the trackpad is that the tap-to-click function is not accepted at all times. For example, you tap on a hyperlink, and nothing happens. Or, you tap on another tab in FireFox, but Firefox does not switch to that tab. Sometimes, you tap in the text you are editing, but the mouse pointer does not place the cursor in the place where you tapped. It takes a few taps before the "click" is accepted by the new Macbook. However, this happens intermittently. I started noticing this a few days ago, and normally it happens a few minutes afer I power up my Macbook. Then, it goes away, and the mouse starts working fine again.

    A few days ago, I loaded several shareware programs on my Macbook (FTPd TftpServer, QuickTerm, etc.). I also installed DeepSleep (which is a widget that allows to make the Mac hybernate instead of going to standby in order to preserve battery). I have been hybernating my Macbook for a few days now, and when I turn it on, it comes out of hybernation rather than loading all the way from cold boot). However, I also tried to restart my Macbook when the trackpad problem starts, and it does not help it.

    I am not sure if the new software I loaded causes the problem with the trackpad, or alternatively, if the heat factor plays any role. It appears that after the Macbook has been on for some time, the problem goes away.

    Has anyone experienced this problem yet?

Share This Page