cmdShell

Go to: Synopsis. Return value. Flags. MEL examples.

Synopsis

cmdShell [-annotation string] [-backgroundColor float float float] [-clear] [-defineTemplate string] [-docTag string] [-dragCallback script] [-dropCallback script] [-enable boolean] [-enableBackground boolean] [-exists] [-fullPathName string] [-height int] [-isObscured] [-manage boolean] [-numberOfHistoryLines int] [-numberOfPopupMenus] [-numberOfSavedLines int] [-parent string] [-popupMenuArray] [-preventOverride boolean] [-prompt string] [-useTemplate string] [-visible boolean] [-visibleChangeCommand script] [-width int] [string]

cmdShell is undoable, queryable, and editable.

Return value

In query mode, return type is based on queried flag.

Flags

Long name (short name)	Argument types	Properties
-exists(-ex)
Returns true|false depending upon whether the specified object exists. Other flags are ignored.
-defineTemplate(-dt)	string
Puts a command in a mode where any other flags and args are parsed and added to the command template specified in the argument. They will be used as default arguments in any subsequent invocations of the command when templateName is set as the current template.
-useTemplate(-ut)	string
Force the command to use a command template other than the current one.
-parent(-p)	string
The parent layout for this control.
-enable(-en)	boolean
The enable state of the control. By default, this flag is set to true and the control is enabled. Specify false and the control will appear dimmed or greyed-out indicating it is disabled.
-width(-w)	int
The width of the control. The control will attempt to be this size if it is not overruled by parent layout conditions.
-height(-h)	int
The height of the control. The control will attempt to be this size if it is not overruled by parent layout conditions.
-visible(-vis)	boolean
The visible state of the control. A control is created visible by default. Note that a control's actual appearance is also dependent on the visible state of its parent layout(s).
-visibleChangeCommand(-vcc)	script
Command that gets executed when visible state of the control changes.
-isObscured(-io)
Return whether the control can actually be seen by the user. The control will be obscured if its state is invisible, if it is blocked (entirely or partially) by some other control, if it or a parent layout is unmanaged, or if the control's window is invisible or iconified.
-manage(-m)	boolean
Manage state of the control. An unmanaged control is not visible, nor does it take up any screen real estate. All controls are created managed by default.
-numberOfPopupMenus(-npm)
Return the number of popup menus attached to this control.
-popupMenuArray(-pma)
Return the names of all the popup menus attached to this control.
-preventOverride(-po)	boolean
If true, this flag disallows overriding the control's attribute via the control's right mouse button menu.
-annotation(-ann)	string
Annotate the control with an extra string value.
-backgroundColor(-bgc)	float float float
The background color of the control. The arguments correspond to the red, green, and blue color components. Each component ranges in value from 0.0 to 1.0. When setting backgroundColor, the background is automatically enabled, unless enableBackground is also specified with a false value.
-enableBackground(-ebg)	boolean
Enables the background color of the control.
-docTag(-dtg)	string
Add a documentation flag to the control. The documentation flag has a directory structure like hierarchy. Eg. -dt render/multiLister/createNode/material
-dragCallback(-dgc)	script
Adds a callback that is called when the middle mouse button is pressed. The MEL version of the callback is of the form: global proc string[] callbackName(string $dragControl, int $x, int $y, int $mods) The proc returns a string array that is transferred to the drop site. By convention the first string in the array describes the user settable message type. Controls that are application defined drag sources may ignore the callback. $mods allows testing for the key modifiers CTL and SHIFT. Possible values are 0 == No modifiers, 1 == SHIFT, 2 == CTL, 3 == CTL + SHIFT. In Python, it is similar, but there are two ways to specify the callback. The recommended way is to pass a Python function object as the argument. In that case, the Python callback should have the form: def callbackName( dragControl, x, y, modifiers ): The values of these arguments are the same as those for the MEL version above. The other way to specify the callback in Python is to specify a string to be executed. In that case, the string will have the values substituted into it via the standard Python format operator. The format values are passed in a dictionary with the keys "dragControl", "x", "y", "modifiers". The "dragControl" value is a string and the other values are integers (eg the callback string could be "print '%(dragControl)s %(x)d %(y)d %(modifiers)d'")
-dropCallback(-dpc)	script
Adds a callback that is called when a drag and drop operation is released above the drop site. The MEL version of the callback is of the form: global proc callbackName(string $dragControl, string $dropControl, string $msgs[], int $x, int $y, int $type) The proc receives a string array that is transferred from the drag source. The first string in the msgs array describes the user defined message type. Controls that are application defined drop sites may ignore the callback. $type can have values of 1 == Move, 2 == Copy, 3 == Link. In Python, it is similar, but there are two ways to specify the callback. The recommended way is to pass a Python function object as the argument. In that case, the Python callback should have the form: def pythonDropTest( dragControl, dropControl, messages, x, y, dragType ): The values of these arguments are the same as those for the MEL version above. The other way to specify the callback in Python is to specify a string to be executed. In that case, the string will have the values substituted into it via the standard Python format operator. The format values are passed in a dictionary with the keys "dragControl", "dropControl", "messages", "x", "y", "type". The "dragControl" value is a string and the other values are integers (eg the callback string could be "print '%(dragControl)s %(dropControl)s %(messages)r %(x)d %(y)d %(type)d'")
-fullPathName(-fpn)	string
Return the full path name of the widget, which includes all the parents
-prompt(-pr)	string
The text that is used as a prompt.
-clear(-cl)
Erases all visible text, and also deletes any text that had scrolled of the top of the field. After clearing the field it will be blank, and you will not be able to scroll up to see previous lines. This flag does not affect the command history buffer, however.
-numberOfSavedLines(-nsl)	int
The total number of lines (the scrolled lines and currently visible lines) that will be remembered by the field. Any lines beyond this number will be lost, and the user will not be able to review them by scrolling. Valid values are 1 through 32767. Any value less than 1 will be handled as if 1 was specified. Similarly, any value greater than 32767 will be handled as if 32767 was specified.
-numberOfHistoryLines(-nhl)	int
The number of input lines to be saved in the command history buffer. You can cycle through this buffer by pressing the up and down arrow keys. Valid values are 0 through 32767. Any value less than 0 will be handled as if 0 was specified. Similarly, any value greater than 32767 will be handled as if 32767 was specified.

Flag can appear in Create mode of command	Flag can appear in Edit mode of command
Flag can appear in Query mode of command	Flag can be used more than once in a command.

MEL examples

//    Delete the window if it already exists.
//
if (`window -exists ExampleWindow`) deleteUI -window ExampleWindow;

//    Create a window containing a cmdShell and a couple buttons.
//
//    Use a form layout to position the controls.
//
window -widthHeight 300 300 ExampleWindow;
string $form = `formLayout`;
string $cmdShell = `cmdShell`;
string $clearButton = `button -label "Clear"
    -command ("cmdShell -edit -clear $cmdShell")`;
string $closeButton = `button -label "Close"
    -command ("deleteUI -window ExampleWindow")`;

//    Set up the attachments.
//
formLayout -edit
    -attachForm     $cmdShell    "top"    0
    -attachForm     $cmdShell    "left"   0
    -attachControl  $cmdShell    "bottom" 0 $clearButton
    -attachForm     $cmdShell    "right"  0

    -attachNone     $clearButton "top"
    -attachForm     $clearButton "left"   0
    -attachForm     $clearButton "bottom" 0
    -attachPosition $clearButton "right"  0 50

    -attachNone     $closeButton "top"
    -attachPosition $closeButton "left"   0 50
    -attachForm     $closeButton "bottom" 0
    -attachForm     $closeButton "right"  0
    $form;

showWindow ExampleWindow;