Return to Answer

It’s probably your touchpad’s “palm-check” setting. The touchpad drivers has a setting which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 5), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1). If that doesn’t work, then check the other accidental-click setting. Depending on your laptop and driver versions, it could be under Tapping (figure 2), called TouchCheck (figure 3), or labeled with the word “delay”. In any case, it will be exposed somewhere in the configuration applet, but you may have to actually read the descriptions or use the context-sensitive help ([?] button)

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows 8

Screenshot of Elantech Tapping setting

Figure 2: Screenshot of Elantech Tapping setting

Figure 3: Screenshot of TouchCheck setting

Figure 4: Screenshot of touchpad delay setting

Figure 5: Photo of laptop keyboard with touchpad below

It’s probably your touchpad’s “accidental-click” counter-measure. The touchpad drivers has one or more settings which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 6), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1). If that doesn’t work, then check the other accidental-click setting. Depending on your laptop and driver versions, it could be under Tapping (figure 2), called TouchCheck (figure 3), or labeled with the word “delay”. In any case, it will be exposed somewhere in the configuration applet, but you may have to actually read the descriptions or use the context-sensitive help ([?] button)

Also, check that regular tap-clicking isn’t being interfered with by the dragging function (figure 5). If you have that set too low, it might be trying to initiate a mouse-drag instead of registering a mouse-click.

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows 8

Screenshot of Elantech Tapping setting

Figure 2: Screenshot of Elantech Tapping setting

Figure 3: Screenshot of TouchCheck setting

Figure 4: Screenshot of touchpad delay setting

Figure 5: Screenshot of touchpad-drag setting

Figure 6: Photo of laptop keyboard with touchpad below

It’s probably your touchpad’s “palm-check” setting. The touchpad drivers has a setting which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 2), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1 and 2).

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows 8

Figure 2: Screemshot of PalmTracking setting in Elantech driver in wattOS!

Figure 2: Photo of laptop keyboard with touchpad below

It’s probably your touchpad’s “palm-check” setting. The touchpad drivers has a setting which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 5), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1). If that doesn’t work, then check the other accidental-click setting. Depending on your laptop and driver versions, it could be under Tapping (figure 2), called TouchCheck (figure 3), or labeled with the word “delay”. In any case, it will be exposed somewhere in the configuration applet, but you may have to actually read the descriptions or use the context-sensitive help ([?] button)

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows 8

Screenshot of Elantech Tapping setting

Figure 2: Screenshot of Elantech Tapping setting

Figure 3: Screenshot of TouchCheck setting

Figure 4: Screenshot of touchpad delay setting

Figure 5: Photo of laptop keyboard with touchpad below

It’s probably your touchpad’s “palm-check” setting. The touchpad drivers has a setting which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 2), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1 and 2).

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows

Figure 2: Screemshot of PalmTracking setting in Elantech driver in wattOS!

Figure 2: Photo of laptop keyboard with touchpad below

It’s probably your touchpad’s “palm-check” setting. The touchpad drivers has a setting which allows it detect what is presumed to be unintentional touchpad input.

It makes sense to check for this because as you can see below (figure 2), laptops have the touchpad in front of the keyboard, so when you are typing, your palm could press on the touchpad and move the cursor or even click the button. The drivers usually accomplish this accidental-input detection by discarding touchpad input while keys are being pressed because they assume you are typing.

Not surprisingly, this causes trouble when you want to press keys and use the touchpad at (or nearly) the same time (for example, when playing games like shooters that require you to hold keys and move the cursor at the same time).

To reduce false-positives, the detection routines usually use the touchpad input as a metric as well, for example by checking if the touch is a large area like a palm instead of just a finger. You can usually adjust the triggering threshold or turn it off altogether. In your case, you will want to try lowering the threshold; try lowering it a little at a time until you find a perfect balance for how you work.

There’s no need to mess with the registry, the setting is exposed in the touchpad’s normal configuration dialog. In your case, the Elantech drivers call it “PalmTracking” (figures 1 and 2).

Figure 1: Screenshot of PalmTracking settingin Elantech driver in Windows 8

Figure 2: Screemshot of PalmTracking setting in Elantech driver in wattOS!

Figure 2: Photo of laptop keyboard with touchpad below