2010

Table Of Contents
In the Script Editor window, ensure that there is not a check mark beside
History > Echo All Commands.
To observe script history
1 In the Script Editor, click the Clear History button.
You can more easily isolate the command history created by the
commands you perform when there is no other history in the Script
Editor.
2 From the Shelf, select the Surfaces tab in order to view the tools located
on that shelf.
3 Click the NURBS Sphere button on the Surfaces Shelf.
Command history is displayed in the history section of the Script Editor:
CreateNURBSSphere;
sphere -p 0 0 0 -ax 0 1 0 -ssw 0 -esw 360 -r 1 -d 3 -ut 0 -tol
0.01 -s 8 -nsp 4 -ch 1;objectMoveCommand;
Several MEL commands are executed when the Shelf button is pressed.
The following happens when the button is pressed:
The NURBS Sphere button on the surfaces Shelf executes a script called
CreateNURBSSphere;.
The CreateNURBSSphere script calls the sphere MEL command using
flags to set the arguments of the command to the values currently
specified in the NURBS Sphere menu option window. The sphere MEL
command is using flags in short form.
The objectMoveCommand is executed every time a primitive is created.
It moves the created object to the origin.
Commands in MEL must be separated with semicolons. Additional spaces
and additional carriage returns do not affect the execution of the scripts.
Blank spaces and returns make scripts easier to read. Flags cannot be
separated from the hyphen character by extra spaces or returns.
Observing script history | 659