In most cases, where a UPDD Client application is responsible for touch control, it is likely to be the main/or only client handling the touch interface.
However, in cases where two or more client apps want to process touch, it is important that there is a degree of co-operation between client apps, so as to avoid touch conflicts between competing applications.
In most cases, with UPDD software, the clash will be between UPDD utility applications themselves or the user client app and the UPDD utility client applications.
To avoid the clash with the various UPDD utility applications; Commander, Annotate and Test, we utilise an internal priority system and the driver delivers touch data to the highest priority app.
In the case of the UPDD client apps, the highest priority is Test, followed by Annotate and then Commander. If none of these are loaded, the API is delivered to all user client applications.
However, in systems where UPDD Commander is utilised, this means that there is always a UPDD Client app taking priority over any user written apps as it is always active, and will only stop processing touch if Test or Annotate are running.
To cater for this situation, such that User client apps are not blocked from receiving touch data whilst Commander is active, we have introduced a mechanism whereby an application can instruct Commander to pass through touch data to the application.
This is configured within Commander as follows:
Use the 'Add New Application' option to add the UPDD Client App into the Application list.
In this example, we selected and added an Application called Flexi-deck, as listed in the Application list:
Now add the special 'All Touches' item to instruct Commander to pass through all touch data to the application:
If you would also like the standard Commander gesture/action processing to be active within your application, select the 'Alongside Gesture' option above. You can tailor the inherited set of gestures / actions as required by your application.
At this point, the client app should receive touch data.
To avoid having to perform the above with each install, you can save the application to a preset file.
This file can then be either loaded from the Commander file menu, Import Application Settings... (as seen above) or, if you receive a branded or tailored driver from Touch-Base, passed to us for inclusion in your software build.
When included in a driver build, the preset will be automatically loaded by Commander if the application is found on the system at install time, or can be loaded manually from the Commander file menu.