toolButton is undoable, queryable, and editable.
This command creates a toolButton that is added to the most
recently created tool button collection unless the
In query mode, return type is based on queried flag.
Long name (short name) |
Argument types |
Properties |
exists(ex) |
boolean |
 |
|
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) |
boolean |
 |
|
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. |
|
|
boolean |
 |
|
Return the number of popup menus attached to this control. |
|
|
boolean |
 |
|
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 |
|
image1(i1) |
string |
   |
|
image2(i2) |
string |
   |
|
image3(i3) |
string |
   |
|
This control supports three images. The image that best fits
the current size of the control will be displayed. This flag
applies the image to the current tool. |
|
imageOverlayLabel(iol) |
string |
   |
|
A short string (5 characters) label that will be displayed on
top of the icon. |
|
toolImage1(ti1) |
[string, string] |
    |
|
toolImage2(ti2) |
[string, string] |
    |
|
toolImage3(ti3) |
[string, string] |
    |
|
This control supports three images. The image that best fits
the current size of the control will be displayed. This flag
applies the image to the specified tool. The first argument is the
name of the tool and the second is the name of the image. When
queried an array of tool icon pairs is returned. |
|
style(st) |
string |
  |
|
The draw style of the control. Valid styles are "iconOnly",
"textOnly", "iconAndTextHorizontal" and "iconAndTextVertical". |
|
onCommand(onc) |
script |
  |
|
Command executed when the control is turned on. |
|
offCommand(ofc) |
script |
  |
|
Command executed when the control is turned off. |
|
changeCommand(cc) |
script |
  |
|
Command executed when the control's state is changed. Note that
this flag should not be used in conjunction with onCommand and
offCommand. That is, one should either use changeCommand and test
the state of the control from inside the callback, or use onCommand
and offCommand as separate callbacks. |
|
collection(cl) |
string |
  |
|
To explicitly add a tool button to a tool collection. |
|
doubleClickCommand(dcc) |
script |
  |
|
Command executed when the control is double clicked. |
|
select(sl) |
boolean |
  |
|
Will set this button as the selected one. This flag also
queries the select state of the control. |
|
tool(t) |
string |
    |
|
The name of the tool to be attached to the button. If the tool
specified is already attached to this button then it will be
selected. Query this flag to return the current tool. This flag may
be specified more than once to attach more than one tool. |
|
allowMultipleTools(amt) |
boolean |
  |
|
Indicates whether this control will allow you to attach more
than one tool. By default, this control accepts only one tool. You
can add multiple tools by setting this flag to true. Only
one tool will be current and displayed at any one time. Use the pop
up menu attached to the right mouse button to view all the
tools. |
|
toolCount(tc) |
boolean |
 |
|
This query only flag return the number of tools attached to the
toolButton control. |
|
toolArray(ta) |
boolean |
 |
|
This query only flag returns the names of all the tools
attached to the toolButton control. |
|
|
boolean |
   |
|
Edit this flag to set the visibility of the popup tool
indicator. The indicator is a simple image that appears in the top
right corner of the button when more that one tool is associated
with this control. This flag is queryable and true by default. |
|