Commander


This document describes how to use and configure UPDD Commander functions. The latest version is compatible with UPDD V6 release 6.0.559 and above.

UPDD Commander brings together a number of functions previously held in separate programs UPDD Gestures and UPDD TUIO and introduces some new features and functions.

One of the main improvements with UPDD Commander if for the ability to associate gesture actions with individual applications so that gesture sets can be defined at the application level rather than a global set of gesture actions that apply across the board for all applications.

Further, the application is written to be cross platform with the aim of bringing similar functionality to the three major desktop systems; Windows, MacOS and Linux whereas UPDD Gestures was previously only available for MacOS.

Following the initial release under MacOS the Windows version was released July 2020. We hope Linux will follow one day!

Commander software will either be installed as part of the UPDD driver installation or directly  from the UPDD application folder; '/library/application support/updd' in MacOS or c:\program files (x86)\updd under Windows.

The vast majority of the UPDD Commander documentation was written for the MacOS implementation of the UPDD Commander software, hence screen shots are all taken from MacOS. In MacOS UPDD Commander implements multi-touch gesture support for touchscreen devices that is normally associated with multi-touch trackpads whereas Windows natively supports the touch interface and gestures so UPDD Commander offers slightly modified functionality when running in Windows as discussed here.

MacOS

When the Commander software is installed as part of the driver installation, start up items are created for all user accounts so that Commander will be running when switching users. Under MacOS the Commander process is installed such that it will be invoked at each system startup.

The UPDD Commander daemon (background) process interacts with the driver and receives all touches from all the touch devices and determines the touch event being performed (i.e. tap, press, gesture) and processes these touches as dictated by the Commander settings.

Gestures are performed on the touch screen exactly as they are on a multi-touch track-pad. The action associated with each gesture can be defined in the touch function dialog. To utilize all available gestures you will need to use a multi-touch touch screen that supports up to 5 touches otherwise you will be restricted to the gestures that relate to the number of stylus supported on the touch screen.  A number of videos have been posted on the web from end uses such as this one here.

When Commander is handling the system pointer the  driver’s own posting of single touch data into the system is disabled and Commander receives all touch from the touch device via the driver’s API interface. If Commander is quit then touch will revert back to single touch via the driver’s own system interface.

Depending on the Commander configuration, it will posts all gesture and touch data as OS X native touch events, as TUIO touches and the UPDD API interface (allows UPDD Client application to receive gesture information), regardless of whether there is a gesture action being performed, as the gestures are more or less separate from the touches themselves.

Where individual gesture processing is not required (you do not require the gesture to trigger any actions for the performed gestures on the touch screen), you can set the gesture action to "No action", and the desktop and  applications will still be able to receive the individual gesture and touch data.

There is also a setting to request that touch data is posted into the system as tablet events, allowing a touch device to be used with Inking and other tablet-related features. It only affects mouse events produced by Gestures, though, since in OS X a tablet event is also a mouse event.

UPDD Commander also supports pen devices that present proximity, left click (via nib), right click, barrel button, pressure and eraser features as described here.

Windows

When the Commander software is installed as part of the driver installation, the installation can be configured to start up for all users. If it is not started automatically as part of the installer there is a global setting in the UPDD Commander dialog to 'Run at startup'

The UPDD Commander daemon (background) process interacts with the driver and receives all touches from all the touch devices and determines the touch event being performed (i.e. tap, press, gesture) and processes these touches as dictated by the Commander settings.

Gestures are performed on the touch screen exactly as they are on a normal Windows monitor or multi-touch track-pad. The action associated with each gesture can be defined in the touch function dialog. To utilize all available gestures you will need to use a multi-touch touch screen that supports up to 5 touches otherwise you will be restricted to the gestures that relate to the number of stylus supported on the touch screen.

When Commander is handling the system pointer the  driver’s own posting of  touch data into the system is disabled and Commander receives all touch from the touch device via the driver’s API interface. If Commander is quit then touch will revert back to touch via the driver’s own system interfaces.

Depending on the Commander configuration, once the gesture is determine and any related action performed the touch data may then be posted to the OS, as TUIO touches and the UPDD API interface (allows UPDD Client application to receive gesture information), regardless of whether there is a gesture action being performed, as the gestures are more or less separate from the touches themselves.

Where individual gesture processing is not required (you do not require the gesture to trigger any actions for the performed gestures on the touch screen), you can set the gesture action to "Post data to Windows", and the desktop applications will still be able to receive the touch data.

Search