Configure gestures for touch devices
- Last UpdatedDec 09, 2024
- 2 minute read
InTouch Access Anywhere automatically detects if a portable device is touch capable and automatically uses the built-in virtual keyboard for text input and gesture support for display navigation. InTouch Access Anywhere supports Windows multi-touch gesture redirection. All multi-touch gestures are redirected natively into the Windows session for use by an application running inside an Access Anywhere session.
Multi-touch gesture redirection feature is enabled using the Access Anywhere Toolbar button and by config.js settings.
Activation Criteria
Access Anywhere multi-touch gesture redirection is enabled and activated based on the following criteria:
Multi-touch gesture redirection functionality is enabled if all of the following are true:
-
Touch is supported by the remote RDP host
-
Touch is supported by the user's computer or mobile device
-
Touch redirection is enabled by setting rdpTouchEnabled to True in the config.js file
Multi-touch gesture redirection can be activated if all of the following are true:
-
Touch feature is enabled
-
Toggle MultiTouch icon is set to active on the Access Anywhere toolbar
-
Touch is not suspended by the RDP host
Toolbar button
Users enable and disable the Windows multi-touch gesture redirection feature by toggling the Toggle MultiTouch icon in the Access Anywhere toolbar, which is enabled by default.
|
Multi-Touch Enabled |
Multi-Touch Disabled |
|
|
|
Multi-touch Gesture Redirection Settings in the Config.js File
The Config.js file is located in the folder path of the computer hosting the InTouch Access Anywhere server:
C:\Program Files (x86)\Wonderware\InTouch Access Anywhere Server\WebServer\AccessAnywhere
|
Config.js Settings |
Description |
|
rdpTouchEnabled |
True (default) - enable remote touch. On the Server: enable the feature, create RDP dynamic virtual channel, and send RDP client touch events. On the Client – enable the feature, process the incoming server touch messages. |
|
rdpTouchActive |
False (default) – Sets the default activation state (ignored when not enabled.) On the Client this is the initial state of the toolbar button. If active, send touch events. |
|
rdpTouchAction |
0 (default) - Action to be taken if multi-touch redirection is enabled, but is not supported by the server or client device. Action codes and their assigned values: 0 - no action 1 - display an error message 2 - display an error message and disconnect from the session 3 - ask for user confirmation to continue without touch |
Conflict with Local Gesture Usage
When multi-touch redirection is enabled, all gestures are redirected to the remote session. However, the user may need to use gestures locally on the device to pan and zoom around the session. When local gesture functionality is required, disable multi-touch redirection temporarily, and re-enable it when it is needed again.