This layout arranges children in a grid fashion where every cell in the grid is the same size. You may specify the number of rows and columns as well as the width and height of the grid cells.
Long name (short name) | Argument Types | Properties | |
---|---|---|---|
allowEmptyCells (aec) | bool | ||
Specify true if you want free positioning of the children in the layout and potentially leaving empty cells between children. Set to false if you want the children to always be packed together. The default is true. |
|||
annotation (ann) | unicode | ||
|
|||
autoGrow (ag) | bool | ||
Specify true if you want the grid layout size to grow as children are added. For example, if the grid layout has 2 columns and 2 rows then adding a fifth child will cause the grid to expand to 3 rows if this flag is true, otherwise the grid will remain the same size and the new child will be hidden from view until you expand the size of the grid using the appropriate flags. The default is true. |
|||
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. |
|||
cellHeight (ch) | int | ||
|
|||
cellWidth (cw) | int | ||
|
|||
cellWidthHeight (cwh) | int, int | ||
|
|||
childArray (ca) | bool | ||
|
|||
columnsResizable (cr) | bool | ||
Specify true if you want the number of columns to adjust according to the width of the layout. Set to false if you want the number of columns to remain fixed when the width of the layout is changed. The default is false. |
|||
defineTemplate (dt) | unicode | ||
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. |
|||
docTag (dtg) | unicode | ||
|
|||
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 dragControlvalue 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 dragControlvalue 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’ |
|||
enable (en) | bool | ||
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. |
|||
enableBackground (ebg) | bool | ||
|
|||
exists (ex) | bool | ||
|
|||
fullPathName (fpn) | unicode | ||
|
|||
gridOrder (go) | bool | ||
|
|||
height (h) | int | ||
|
|||
isObscured (io) | bool | ||
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) | bool | ||
|
|||
numberOfChildren (nch) | bool | ||
|
|||
numberOfColumns (nc) | int | ||
|
|||
numberOfPopupMenus (npm) | bool | ||
|
|||
numberOfRows (nr) | int | ||
|
|||
numberOfRowsColumns (nrc) | int, int | ||
|
|||
parent (p) | unicode | ||
|
|||
popupMenuArray (pma) | bool | ||
|
|||
position (pos) | unicode, int | ||
Specify the name of a child control in the grid layout along with a 1-based integer value indicating the desired position of the child. Positions increase from left to right within a row and then wrap around to the next row increasing from top to bottom. For example, a grid layout with 3 columns and 2 rows has 6 visible positions where 1, 2 and 3 occupy the first row and 4, 5 and 6 occupy the second. Flag can have multiple arguments, passed either as a tuple or a list. |
|||
preventOverride (po) | bool | ||
|
|||
useTemplate (ut) | unicode | ||
|
|||
visible (vis) | bool | ||
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 | ||
|
|||
width (w) | int | ||
|
Derived from mel command maya.cmds.gridLayout
Example:
import pymel.core as pm
pm.window()
# Result: ui.Window('window1') #
pm.gridLayout( numberOfColumns=2, cellWidthHeight=(50, 50) )
# Result: ui.GridLayout('window1|gridLayout2') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button38') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button39') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button40') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button41') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button42') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button43') #
pm.button()
# Result: ui.Button('window1|gridLayout2|button44') #
pm.showWindow()