DIAMONDTOUCH(4)DIAMONDTOUCH(4)NAME
diamond - X driver for the MERL DiamondTouch
SYNOPSIS
Section "InputDevice"
Identifier "devname"
Driver "diamondtouch"
Option "Device" "devpath"
Option "NumDevices" "1"
Option "RowThreshold" "60"
Option "ColThreshold" "60"
Option "SearchFunction" "function"
Option "DeliverBlobs" "True"
Option "MoveThreshold" "30"
Option "NoiseLimit" "5"
Option "UserNumber" "0"
...
EndSection
DESCRIPTIONdiamondtouch is an Xorg input driver for the MERL DiamondTouch devices.
The diamondtouch driver is a pointer emulation for the touchpoints
detected on the device. It can be used as the core pointer.
If multiple input devices are configured for the same device path, they
will be assigned to the different users on this device. By default,
the driver will send blob events to the X server and let the server
emulate a pointer event. Blob events can be switched off and pointer
emulation has to happen in the driver.
CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details and for
options that can be used with all input drivers. This section only
covers configuration details specific to this driver.
OPTIONS
The following driver Options control what devices are accepted:
Option "Device" "string"
Specifies the device node through which the device can be
accessed. Default is /dev/DiamondTouch. Multiple X devices
using the same device path will be assigned to the different
users on the physical device.
Note that a DiamondTouch device has a maximum number of users.
Once this maximum is reached, additional X device will fail to
initialize.
Option "Name" "string"
Specifies the device name for the device you wish to use.
It probably helps if you assign some meaningful name to the
device, so an X client has some way of knowing what the device
actually is. Think "DT User 1" or the like.
Option "NumDevices" "string"
Specifies how many recursive devices to create.
If multiple devices should be created from one physical device,
this option causes the driver to recursively create additional
devices. For example, if NumDevices is 4, this driver creates
four devices without the need to have four separate sections in
the xorg.conf. Default is 1.
Option "RowThreshold" "integer"
Specifies the lower threshold to accept a signal from the
device. Any rows with a singal strength lower than the threshold
will be ignored. Default is 60.
Option "ColThreshold" "integer"
Specifies the lower threshold to accept a signal from the
device. Any columns with a singal strength lower than the
threshold will be ignored. Default is 60.
Option "SearchFunction" "string"
Specifies the search function to be used for finding a hotspot.
This setting is only used if blob events are disabled. Supported
functions are:
SignalPeak takes the highest value for rows/columns each and
uses them as a hotspot. Default setting.
BBCenter calculates the bounding box around all touches from the
same user and uses the center of the bounding box as hotspot.
Option "UserNumber" "integer"
Specifies the user number on the device (essentially the pad the
user has to touch). Valid options are 0 to the maximum number of
users of the device. Default setting is to take the next avail‐
able user number.
If the same user is added twice, the server will not create a
new device. An error message is printed to the log.
If a UserNumber is supplied that is greater than the number of
users supported by the device, the server will not create a new
device. An error message is printed to the log.
BUGS
Only works for a single screen.
The mapping from device coordinates to screen coordinates is crude and
can result in jumpy cursors.
The signal strenght is not reported to the client.
NumDevices does not forward options (e.g. RowThreshold) to the recur‐
sively created devices.
DEPRECATED OPTIONS
The following driver Options are deprecated in the current version.
They require a now-orphaned branch of the X server.
Option "DeliverBlobs" "boolean"
Specify if blob events should be generated by this device.
Default is TRUE.
Option "MoveThreshold" "integer"
Threshold in pixels when to consider a blob a continuation blob.
If the edges of a blob are within this threshold to the position
a previous blob, it is considered a continuation of the blob.
This value does not apply if there is only one blob detected.
Default is 30.
Option "NoiseLimit" "integer"
Minimum amount of pixels a blob has to move before it sends a
new event. If either bounding box or hotspot moves more than
the NoiseLimit value, then a new event is set. If the bitmap
data changes, a new event is set regardless of the NoiseLimit
setting. Default is 5.
AUTHORS
Peter Hutterer
SEE ALSOXorg(1), xorg.conf(5), xorgconfig(1), Xserver(1), X(7).
X Version 11 xf86-input-diamondtouch 0.3.0 DIAMONDTOUCH(4)
