|
UPDDdraw
is used to simply test the performance and accuracy of the touch device as
handled by the UPDD driver. It can be used to view stylus input from single
and multi-touch devices.
This
document refers to the UPDDdraw supplied with UPDD version 5.1.1314 and
above.
Invoking draw
UPDDdraw
can be invoked in various ways:
|
Windows
|
|
|
Program
Manager, UPDD entry
|
|
|
Runs
draw on the monitor associated with the first UPDD device.
|
|
|
Windows
|
Mac
OS X
|
Linux
|
|
UPDD
system tray or menu item
|
|
|
|
|
Runs
draw on the monitor associated with the first UPDD device or offers a
selection of configured devices in multi touch device configuration.
|
|
Windows,
Mac OS X, Linux
|
|
UPDD
Console, Status
|
|
|
Runs
draw on the monitor associated with the currently selected device in the
UPDD Console. Show test grid invokes draw with a grid displayed in the
drawing area.
|
Draw parameters
UPDDdraw
utility can accept a number of parameters as follows:
|
/test
|
Brings
up maximised
|
|
/grid
|
Brings
up maximised with grid background
|
|
/fullscreen
|
Run
in full screen mode – implemented in some UPDD distributions at the request
of OEMs
|
|
/touchmode
|
Start
in touch
mode
– UPDD 5.1.1314
|
|
/calibrated
|
start
in calibrated mode, also sets touchmode – UPDD 5.1.1314
|
|
/device
n
|
Invoked
on the desktop associated with a specific device
|
Dialog and functionality
When
invoked, the dialog is shown as below:
The
dialog has four main areas, Menu, Functions, Drawing and Status:
|
Menu
|
File
|
New,
Open and save captured drawings
|
|
|
View
|
Allows
status area to be enabled or disabled
Allows Calibrated mode to be selected (since UPDD 5.1.1314)
Note
that to use Calibrated Mode, you must first select “touch mode” and have
started updddraw for a specific device (/device n)
Starting
updddraw using one of the console options always sets a specific device.
Note
that if the monitor configuration changes (number, position or arrangement
of monitors) then updddraw must be restarted to recognise this in
calibrated mode.
|
|
|
Help
|
Draw
information
|
|
Functions
|
|
|
|
New
|
|
Starts
new drawing session
|
|
Open
|
|
Open
previously saved images
|
|
Save
|
|
Save
current drawing
|
|
Colour
|
|
Select
pen colour
|
|
Width
|
|
Select
pen width
|
|
Clear
|
|
Clear
drawing
|
|
Snap
|
|
Snapshot
desktop into drawing area
|
|
Mode
|
|
Toggle
between mouse emulation and touch mode. See Mode of Operation section below
|
|
|
|
Mouse emulation mode.
|
|
|
|
Touch mode.
|
|
Full Screen
|
|
Enter
full screen mode – Mainly used to test full screen calibration accuracy.
Keeps the current mode of operation
|
|
Info
|
|
UPDD
draw general information
|
|
Cancel
|
|
Close
(dialog or status area)
|
|
Drawing
|
|
Drawing
area
|
|
Status
|
|
Stylus
data, content depending on mode of operation
|
Mode of operation
The
draw utility can run in Mouse emulation mode or direct mode.
|
Mouse
|
Drawing
reflects the single touch mouse movement. In this mode the drawing also
reflects the calibration of the device so the pen drawing is only seen when
the mouse pointer is in the draw area.
Status
information reflects the mouse clicks and desktop video co-ordinate as
shown in the following example:
|
|
|
|
|
|
This
status output reflects two touches, one after another, passed to the mouse
port (by the default stylus) that generated Mouse left button down and up
and shows the calculated video co-ordinates.
|
|
Touch
|
Drawing
reflects data seen directly from all touch devices and all stylus via the
UPDD API interface.
Starting
with version 5.1.1314 in touch mode, if a specific device is selected
(/device n) then only drawing from the specified device is shown. Starting
updddraw using one of the console options always sets a specific device.
By
default, touch mode drawing is scaled into the drawing area so will
not reflect calibration but will show the drawing from the full
extent of the device. UPDD 5.1.1314 introduced a calibrated mode.
Touch mode must be used to see data from a dual or
multi touch device.
Status
information shows some of the information available at the API level of
interface as shown in the following example:
|
|
|
|
|
|
The
above status output shows two touches, one after another, where the data is
received directly from a single stylus on a touch device and the events
generate by the driver for each touch.
Import
note: Given that mouse emulation is disabled in this mode the dialog
functions cannot be activated via touch, as per this warning message, shown
in UPDD 5.1.x:
|
|
|
Touch
stylus
|
Indicates
stylus number, 0, 1, 2 etc. Drawing is colour coded with different colours
used per stylus. Stylus 0 uses currently selected colour.
|
|
|
Mouse
event
|
The
mouse event relating to current UPDD mouse click settings.
|
|
|
Pen
up trigger
|
Non-timed:
Pen up touch data packet received.
Timed:
Driver generated due to lift off time setting trigger.
|
|
|
Raw
device co-ordinates
|
Raw
co-ordinates generated by the device.
|
|
|
Calibrated
co-ordinates
|
Video
co-ordinates as calculated from the calibration data.
|
Touch Logging
When
updddraw is operating in touch mode a log file (updddraw.log) is created.
This is in a format useful to Touch-Base support. This will be written to
the UPDD folder (entry “updd folder” in tbupdd.ini) if the user has
permissions for this, else in the temp folder. Under Windows the temp folder
location can be retrieved by the command ‘set temp’. Under Linux and Mac the
file is written to /tmp. This function was introduced to capture touch data
for debugging purposes, especially when trying to understand unexpected touch
movements.
This
feature requires that the packet
disposition
be set to allow concurrent touch and raw data processing. Starting with
version 5.1.1314, when touch mode is first selected, the current disposition
is patched, to set all endpoints to “b” (both). This setting is reverted when
the utility closes. This is not normally of concern to end users; but it is
possible that if, for example, a system with a complex configuration with specific
disposition requirements is in use and it is rebooted whilst updddraw is
active in touch mode this setting can be disrupted. In the unlikely event
that this occurs and causes a problem the easies course of action is to
reinstall the driver.
Toolbars
Systems
utilising UPDD toolbars can view toolbar
information in UPDD draw (from UPDD build 1274 onwards) as
shown in the following example:
In
this example a toolbar, named ‘action’ is in use to utilise UPDD desktop
annotate functions to allow live annotation over a Windows desktop. As each
toolbar cell is touched relevant toolbar information is displayed in the UPDD
draw status area.
Example
In
the following example UPDD Draw is placed in touch mode to show the drawing
and stylus information seen simultaneously from both stylus of a dual touch
device:
Contact
For further information or technical
assistance please email the technical support team at technical@touch-base.com
|
