Editing Scripts

Regardless of how a script is created, edit it using either the Script Editor or a text editor. You can debug a TE Client script from the TE Text Editor or have the script generate a log file. Once you have completed editing the script you can export the script to use on a different device or deploy it for use during an emulation session.

When the script generates a log file, each action executed, with the values of its arguments and the results of the action, is written to the log file. The file path for where the log file is stored is configured using the Logging_On action.

When a script calls another script, the logging for the calling script is suspended. Logging resumes when the called script exits. It is possible to have a script called by another script (or a script calling itself recursively) use the same logging file.

Turn Script Logging On

Turn Script Logging Off

To debug a script:

1  From the main screen of the Script Editor, click Add As Text to open the Text Editor.

2  Build your script. When your script is complete, click Build to verify the script text.

The Text Editor displays build information in the bottom section of the window.

3  If the build information includes an error message, click the message to display the Script Editor Error Help dialog box.

The Script Editor Error Help dialog box displays the error number, a description of the error, and explains how to fix the error.

To edit a script with the Text Editor:

1  Launch the Script Editor.

2  Select the script you want to edit from the script list and click Edit As Text.

The Text Editor appears.

3  Edit the script as desired, then click Build to verify the script syntax.

4  When you have finished editing the script, click Save or Save As to save a copy of the script text.

5  Click Done to return to the Script Editor, or click Open to edit another script.


Was this article useful?    

The topic was:



Not what I expected


© 2016 Wavelink Corporation. All Rights Reserved.