13
G&
GLIN
TM
Defining and storing macros
Macros are simple but very efficient accelerators in many situations. An easy and automatic way of obtaining
a correct, working macro is to record your dialog with the legacy application. You turn on Glink’s macro
definition function in the edit menu at the point where you are about to begin the dialog that you will later
replace with the macro. At the end of the sequence you turn it off in the same menu.
Turning off the macro definition triggers the Glink macro storage dialog
box. You can save the macro as the current in-line macro, which makes it
available for use at any time from the edit menu. You can save it in your
keyboard configuration macro library, where there is space for storing
1000 macros. The macro can then be assigned to a keyboard sequence,
Keyboard bar, Function bar or to a menu item. Finally you can save the
macro as a script file. This stores the macro as a simple Glink script that
delivers the same keyboard input as you did when you defined the
macro.
Defining and storing scripts
The Glink script language is a very powerful tool for increasing the productivity of users accessing legacy
applications. The language has a wide range of features that make Glink unique in the emulator market as
regards script functionality. You must compose complex scripts using a text editor, but you can accomplish
many tasks that are too complex for a macro using an automatically generated script. You turn on the script
definition feature using the ‘Learn’ icon in the Toolbar, or the ‘Learn mode’ entry in the Edit menu.
This triggers the script generation feature and you are requested to
name the script. The script will be stored in your script directory if
you have one, or otherwise in your Glink directory.
The script will begin by connecting if you are not already connected
to the mainframe, and so you are requested to give the name for the
connect, with a default of the mainframe in your current Glink
configuration.
You choose between simple and advanced mode.
Simple mode just records each of your input messages,
but the prompt from the legacy application is remembered.
This means that if unexpected legacy application
messages are received your script will not reply until it
sees the correct prompt
Advanced mode allows you to specify output messages as
patterns that can be recognized, and trigger the same input
each time. This is useful when the legacy application
pages output with a given prompt, and needs an answer to
continue.
You terminate learn mode with the Escape key, and this triggers a dialog that allows you to immediately
assign your script to your toolbar if desired:
Regardless of your choice, the script
is stored in your script directory, and
from there can be assigned to a
keyboard sequence, Keyboard bar,
Function bar, or to a menu item.
(9 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais