Command files are simple ASCII text and can be edited with any text editor. To easily determine the command for a given action, open the Command dialog and watch the list above the current line as you perform various operations. Keep in mind that the successful execution of some commands depends on the proper state existing at the time of execution. For example, creating a part when the parent part (as referenced by the part number) does not exist will cause an error.

Command files can be nested: if you have a file that performs a certain task, you can call that command file from another file with the play: filename command. When a play: command is executed, the command file being played will be expanded in the History window, in a different color below the current line. Check the Expand playfiles box to expand all played files ahead of time. When played files are nested, their commands will be shown in red, yellow, green, blue and black respectively.

An exit: command will cause EnSight to quit. An interrupt: command will cause the command file to pause execution and open the command dialog.

You can save the command file for the current session when you exit EnSight, or you can use File → Save → Command from this session... to save the commands up to that point

Command language can be used to generate macros. See Define and Use Macros.

In addition to command files and macros, you also access the python interface through this dialog. This is explained in detail in the Interface Manual. See Python EnSight module interface.