Udostępnij za pośrednictwem

Test.Aliasing (bfd64bac-b26c-44af-96fd-b78c09b860c3)

  • Artykuł

The test verifies that the device can track and report unique continually arriving and departing contacts without aliasing at fixed separation distances.

Test details

   
Specifications
  • Device.Input.Digitizer.PrecisionTouchpad.FingerSeparation
  • Device.Input.Digitizer.PrecisionTouchpad.HIDCompliant
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows 10, client editions (Arm64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 2
Category Compatibility
Timeout (in minutes) 120
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

Before you run the test, complete the test setup as described in the test requirements: Mouse or other Pointing Device Testing Prerequisites.

  1. Alternate between 2 fingers ~15mm apart, and tap the touchpad at 240 taps/minute.

    When you tap, hold down a contact until it is time to make another tap with that contact, rather than making light taps (to interleave the down times of the two contacts).

  2. Verify that after tapping for ten seconds, no line is drawn between these contacts (see Common Errors in this topic for an example of a failure).

  3. Repeat steps 1 and 2 by having fingers aligned on the vertical axis.

  4. Repeat steps 1 and 2 by having fingers aligned on the diagonal axis.

  5. Manually pass the iteration if validations in all axes were successful.

  6. Repeat steps 1 through 5 by having fingers ~40mm apart.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Input Testing.

Error Description/Workaround

[20] Positional delta too large ###

Aliasing caused device contact swap, thereby causing the device to report a quick swipe.

The value represents the displacement distance. Any displacement > 270 (2.7mm) causes this error.

 

More information

Command syntax

Command Description

ptlogo.exe Test.Aliasing.json

Runs the test.

 

File list

File Location

ptlogo.exe

<testbinroot>\input\PrecisionTouchpad\

config.json

<testbinroot>\input\PrecisionTouchpad\

Test.Aliasing.json

<testbinroot>\input\PrecisionTouchpad\