Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Editor-Debugger utility is designed for creating, debugging and editing used to create, debug and edit scripts in the Axxon PSIM software package.

Figure shows the The Editor-Debugger dialog window is shown in the figure below.

The Editor-Debugger utility contains the built-in embedded text editor and the debugger debugging window.

To help with writing correct codesscripts, the text editor automatically highlights objects, methods and properties in different colors. In that are a part of the object model of the JScript language. In addition, the code blocks can be collapsed or expanded with - or + buttons in to the left of the Script text field.

Info
titleNote.

When switching between scripts, script messages or other objects in the Editor-Debugger utility tree, the collapsing settings are reset, i.e., it means, all blocks in the script become expanded.

The position of the cursor in each script is stored in the context of within one Axxon PSIM session (the cursor position is reset at the product restart). For example, if you place the cursor at the end of //Line 2 in Script 1, then switch to Script 2 and perform any action in it, the cursor will be still at the end of //Line 2 when you return to Script 1.

The debugger window debugging window of the Editor-Debugger utility allows viewing the information about all events registered by the system. You may can filter the events to be shown that are displayed in the debugger debugging window. A separate debugger debugging window is created for each Script system object, which allows you to debug each script to be debugged individually using the filters.

To debug the script, it is possible to test run using a user-defined test event generated by the utility and not registered in the system. To display or edit this event, select Debug and edit ->  Summary Information, and then go to the Trial event tab on the panel that opens at the bottom of the window. For details, see Creating and using test events.

Scripts can be saved as Script objects or as text files You can save the created script in the Script system object or in a text file on the hard drive.