English

Problem: AML does not pause for input from the keyboard

Solution or Workaround

Description:

AML's do not pause after issuing commands that require user input from the keyboard. Instead, the AML continues using the following lines as input to the previous command. How does AML recognize a request for keyboard input?

Cause:

When you run an AML, the AML takes over the input stream. This means that any command issued will get its required text input from the AML, rather than from the keyboard.

Solution:

When a command requires keyboard input, the command can be preceded by the &TTY directive. For example, when adding ANNOTATION to a coverage in ARCEDIT, the ADD command will read the AML lines as the text to add rather than letting the user input the text. By using '&TTY ADD' instead, the AML will suspend operation for the duration of the command.

NOTE: This does not apply to graphic coordinate entry. If coordinates are expected (as in "MAPEXTENT *" for example), the AML will pause until the coordinates are entered with the current pointing device.