Button setup

Toolbar button N

You can modify this button-position to perform a different function by tapping the Button selected line.

The text displayed on the button can be modified by editing the Button text field. If the button text starts with a *, the button width will be doubled. For example, if the button text is *Enter, the width will be doubled but the button text itself will be Enter. If the button text starts with **Enter, the button width will be tripled and so on.

You can also modify the text displayed on the button for this particular function by editing the Button text field.

If the Button selected is a Macro, you have to define the Macro string to be executed when the button is tapped.

Macro string

When entering the macro definitions there are several conventions you may use, all of which are signalled using the caret (^). If you wish to enter a 'real' caret then you must type it twice (^^).

Control characters may be entered using the normal convention with a letter following the caret symbol. For example, a return is ^M and a line feed is ^J.

You may also send specific ASCII codes in hexadecimal, decimal, or octal form by following the caret with a $, #, or & character, and the desired code:

^#ddd
decimal specification
^&ooo
octal specification
^$hh
hexadecimal specification

Note that decimal and octal codes must be 3 digits and prefixed with 0 if it is 2 digit codes.

Transmitting the string you have defined on a macro can be awkward if you are working in multiple environments where you sometimes need a CR terminator and sometimes need an ETX or EOT. To do this transparently, use the conventional form ^! (caret + exclamation mark). The correct line terminator will be sent depending on the mode in which the emulator is operating. Note that if a macro contains multiple transmits then the macro execution will be suspended on each transmit, and resumed when the host has responded. This functionality is only reliable for host connections with a 'turn' mechanism that signals when the host response is finished (DSA, Ggate and TNVIP).

Function codes (for those using synchronous interfaces) may be sent using the form '^=x', where 'x' is the function code you wish to be sent with the next message to be transmitted.

If the last character in the macro string typed in is '^', it will be ignored. This can in fact be useful: in that trailing spaces are deleted from the input you type, you can use an appropriately placed '^' at the end of the string to ensure that required trailing spaces are actually included. For example, entering 'ABC ^' will provide a trailing space after the 'ABC'.