Navigation settings

The key code to execute when a device user taps a field after the active field. The Client calculates the total number of forward commands needed to reach that field, and then performs the action. The host receives and interprets the commands and returns the desired action.

This option is available for VT100, VT220, and XTERM projects.

If this field is left blank, users cannot navigate forward to new fields by touch. However, physical or software keyboards still allow tabbing forward.

By default, this is set to {TAB}.

If you wish to change this value, your host must support the new command.

The key code to execute when a device user taps a field before the current field. The Client calculates the total number of back commands needed to reach that field, and then performs the action. The host receives and interprets the commands and returns the desired action. By default, this is blank.

If you do not enter a field back command, then the forward command will be used to cycle forward through the fields.

This option is available for VT100, VT220, and XTERM projects.

When a back command is executed from the last field, it does not cause a field submit to the host.

If you wish to change this value, your host must support the new command.

The key code to execute when a device user pushes the hardware Back button. If left blank, the Back button on a device will do nothing.

This option is available for VT, 3270/5250, and Web projects on Android.

Key codes for a menu up key and a menu down key. These are displayed on screens with menus that take more than one screen, where the user needs to page through a menu. On the device toolbar, buttons for Menu Up and Menu Down appear next to the keyboard button. When a button is tapped, the defined key code is sent to the host.

If these fields are left empty, the buttons do not appear when a menu is displayed.

Disables the ability for device users to zoom in or out on a screen. This ensures device users don't accidentally zoom in on screens while performing manual tasks. Users may still touch the screen to select fields or use software keyboards.

Projects created before Velocity v1.2.104 default to No.

This option is only available to TE projects.

Enables the user to scroll up or down, or pan side to side to change the visible area of the screen. If zoom is enabled, that setting overrides this one and scrolling and panning are enabled.

This option is only available to TE projects.

The Client displays the top left portion of the native screen by default and the screen does not follow the cursor when it moves. If you enable scrolling and panning, the device user can move the screen away to a different area of the screen, but each new screen will default to the top left corner.

This option is only available to TE projects.

Hides the Velocity toolbar (with the keyboard button, menu button, shortcut menu button, and the following optional buttons: menu up and down buttons, system keyboard button, and Tabs button) from view. This does not affect Android or Windows system navigation.

If you hide the toolbar, you can use hardware keypresses to bring up the keyboard, menu, or shortcut menu.

This option is available for TE, Web, and SIM projects.

The hex value for a key that opens or closes the menu. This field only accepts the hex values for keys; it does not accept named values or macros.

This option is available for TE, Web, and SIM projects.

The hex value for a key that opens or closes the shortcut menu. This field only accepts the hex values for keys; it does not accept named values or macros.

This option is available for TE, Web, and SIM projects.

For TE or Web sessions: Provide the package name and main activity for an Android app package using the following format:

[package name]/[main activity]

For example: 

com.adobe.reader/com.adobe.reader.AdobeReader

-Or-

com.adobe.reader/.AdobeReader

The Velocity Client displays a button in the toolbar that launches the app on the device.

The behavior of the quick launch feature changed with Android 11 and Velocity 2.1.25. Devices running Android 11 or newer must have the activity name included in order to launch the application. Devices running earlier versions of Android may still work with only the package name.

For Web sessions: Provide a URL to create a button in the Velocity toolbar. Tapping the button navigates to the page using Velocity. This option is available for Velocity 2.1.21 or newer.

For Web sessions, you can set the quick launch to the same address as the host address or a different address. Configuring a quick launch address does not change the function of the Home option in the Shortcut menu.

The Quick launch options are available on Android devices.