Touch Driver Registry Settings (Compact 2013)
3/26/2014
The following examples show registry entries for the touch screen stream interface driver. The examples show values you might set to use the touch screen driver.
[HKEY_LOCAL_MACHINE\Drivers\Touch]
"Prefix"="TCH"
"Index"=dword:1
"Order"=dword:2
"Flags"=dword:8 ; DEVFLAGS_NAKEDENTRIES
"IRQ"=dword:12 ; Platform specific. PDD uses this IRQ to set up its IST.
; IClass = touch driver class and power managed touch device
"IClass"=multi_sz:"{25121442-08CA-48dd-91CC-BFC9F790027C}",
"{7119776D-9F23-4e4e-9D9B-9AE962733770}"
"Priority256"=dword:6D ; touch ist priority = 109
"DLL"="touch.dll"
The following table shows values that might be in HKEY_LOCAL_MACHINE\Drivers\Touch in the Platform.reg file.
Note
The values set under HKEY_LOCAL_MACHINE\Drivers\Touch could also be specified under a registry key such as HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch or HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Tch. When a subkey under HKEY_LOCAL_MACHINE\Drivers\BuiltIn</STRONG> is used, the touch screen driver is loaded by Device Manager instead of GWES. If Device Manager is used to load the touch screen driver instead of GWES, you might experience a slower boot time.
Value : type |
Description |
|---|---|
IRQ : DWORD |
Indicates which touch IRQ the touch interrupt service thread (IST) uses to dynamically allocate a SYSINTR. The process binds the touch IRQ to the allocated SYSINTR if a SYSINTR is not specified. |
SYSINTR : DWORD |
Indicates the SYSINTR used by the touch IST. |
Priority256 : DWORD |
Required. Indicates the IST priority. The touch proxy DLL uses this value to set the priority of the read thread. |
IClass : MULTI_SZ |
Required. The value {25121442-08CA-48dd-91CC-BFC9F790027C} specifies a touch driver. The value {7119776D-9F23-4e4e-9D9B-9AE962733770} specifies a power managed touch driver. |
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"DriverName"="tchproxy.dll"
"CalibrationData"="511,410 254,192 254,624 764,624 768,196"
"MaxCalError"=dword:7
The following table shows values that might be in HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH in the Platform.reg file.
Value : type |
Description |
|---|---|
DriverName |
Value that Common.reg sets to tchproxy.dll. By default, GWES loads tchproxy.dll. |
CalibrationData |
Value that GWES uses to load and store calibration data. Touch calibration data must be specified in the registry. If touch calibration data is not specified in the registry, then touch will not work on the user interface even if the touch screen driver is loaded. CalibrationData can be updated manually using the TouchCalibrate function. |
MaxCalError : DWORD |
Optional. Indicates the maximum calibration error. The touch DLL calibration routines use this value. The default setting is 5. |
[HKEY_LOCAL_MACHINE\System\GWE\TouchProxy]
"tchcaldll"="tchcaldll.dll"
The following table shows information about HKEY_LOCAL_MACHINE\System\GWE\TouchProxy in the Common.reg file.
Value |
Description |
|---|---|
TchCalDll |
Indicates the touch calibration DLL that the touch proxy DLL uses. You can omit this value if the touch driver has its own calibration routines. The default value is TchCalDll.dll. |
The touch proxy DLL loads the touch screen stream interface driver. GWES loads tchproxy.dll. The following example shows the registry entry in public\common\oak\files\common.reg:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"DriverName"="tchproxy.dll"
If your BSP uses the touch driver model where GWES directly loads the touch driver, specify the following touch driver registry entry in platform.reg:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVIECMAP\TOUCH]
"DriverName"="platformtouchdriver.dll"
The registry key HKEY_LOCAL_MACHINE\System\GWE\UserInput\PromoteMouseInputToTouchInput can be used to promote all mouse_event samples as touch. This registry key is only read at device boot up, so the associated functionality can not be switched dynamically by changing the registry key.