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.

The key code for a menu up key. On the device toolbar, this appears to the left or right of the keyboard button. When the button is pushed, the defined key code is sent to the host. If left empty, this button does not appear when a menu is displayed.

The key code for a menu down key. On the device toolbar, this appears to the left or right of the keyboard button. When the button is pushed, the defined key code is sent to the host. If left empty, this button does 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.

The Client displays the top left portion of the native screen. Scrolling is disabled and the user cannot pan or zoom the screen.

This option is only available to TE projects.

Hides the Velocity toolbar (with the keyboard button, menu button, and shortcut menu button) from view. This does not affect the Android bottom navigation bar.

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 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.