Go to: Synopsis. Return value. Keywords. Related. Flags. Python examples.


hudButton([string], [allowOverlap=boolean], [block=int], [blockAlignment=string], [blockSize=string], [buttonShape=string], [buttonWidth=int], [label=string], [labelFontSize=string], [padding=int], [pressCommand=script], [releaseCommand=script], [section=int], [visible=boolean])

Note: Strings representing object names and arguments must be separated by commas. This is not depicted in the synopsis.

hudButton is NOT undoable, queryable, and editable.

This command creates a Heads-up Display (HUD) button control which is placed in a 2D inactive overlay plane on the 3D viewport. It is to be used to provide hands-on interaction designated by a user script. The HUD button is derived from a generic HUD object and thus inherits a similar workflow.

Although this command provides much of the same functionality as the headsUpDisplay command, it does not provide headsUpDisplay layout controls such as layoutVisibility, nextFreeBlock, lastOccupiedBlock, exists, remove, etc. To access that functionality, please use the headsUpDisplay command. This command is focused solely around the creation and management of HUD button controls. Similarly, all operations performed by this command are limited to HUDs that are button controls.

The only mandatory flags, on creation are the section and block flags.

Like the headsUpDisplay command, upon creation of a HUD button, an ID number will be assigned to it. This can be used to remove the HUD via the headsUpDisplay command (-rid/removeID [int IDNumber]), if desired. Alternatively, the headsUpDisplay command can remove HUD objects via their position (section and block), or their unique name.

Return value

intID number of the Heads-Up Display (HUD).
string|int|int[2]HUD name, HUD ID or Section and block value, for respective remove commands.

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


hud, headsupdisplay, button, hudbutton


button, headsUpDisplay


allowOverlap, block, blockAlignment, blockSize, buttonShape, buttonWidth, label, labelFontSize, padding, pressCommand, releaseCommand, section, visible
Long name (short name) Argument types Properties
visible(vis) boolean createqueryedit
Sets the visibility of the Heads-Up Display on and off.
allowOverlap(ao) boolean createqueryedit
Sets the Heads-Up Display to be visible regardless of overlapping section widths/limitations (see -s/section flag description for more details).
section(s) int createqueryedit
Defines the section the HUD will appear in. There are 10 sections divided across the screen. Five columns and two rows make up the ten element matrix which divide the main viewport. Here is a visual layout of the sections.

|    |    |    |    |    |
|    |    |    |    |    |
| 0  | 1  | 2  | 3  | 4  |
|    |    |    |    |    |
|    |    |    |    |    |
|    |    |    |    |    |
| 5  | 6  | 7  | 8  | 9  |
|    |    |    |    |    |

Each section is denoted by a number from 0 to 9 as illustrated above. For example, if the second column of the top row was desired, the section would be defined as: -sec 1

To prevent HUD objects from displaying over each other and causing a clutter of letters, each row has a defined visibility precedence, where each section would have a visibility priority level. Depending on each priority level, when the screen space begins to shrink to a point where the section widths of a given row begin to collide, the HUD automatically compensates for this by removing the sections of least priority. These sections are made invisible and a warning is issued to inform the user of the removal. This continues until only the section of highest priority remains.

For each row, the priorities are defined as follows. Using the top row as an example: Section 0, has the highest priority, followed by Section 4, making the outermost sections of highest priority. Next in the list is Section 2, and lastly Sections 1 and 3 are of the equal and least priority. This priority structure can be applied to the bottom row as well. The two outermost sections have the highest priority, followed by the middle section, and finally the remaining two sections are of lowest priority.

This means that as the viewport gradually decreases in width to the point where sections in the top row begin to overlap, sections 1 and 3 will be removed from view first, followed by section 2, and finally section 4. A similar note is provided below for the block layout.

block(b) int createqueryedit
Denotes the individual block that the HUD will reside in, within a section. Each section is composed of a single column of blocks. The total number of blocks contained within each section is variable.

The number of blocks that will be visible within each section is dependent on the size of blocks contained in each section and the current size of the window. Blocks begin enumerating from 0 and flexibly increase based on need.

For HUD buttons, the format differs from that of the standard HUD. The layout using parameters defined by the formatting flags listed below (eg. justify, padding, buttonWidth) is shown below:

|     |     |          |     |     |
|  P  |  J  |  Button  |  J  |  P  |
P = Sub-block of width, padding
J = Justification of the entire block
Button = Sub-block of width, buttonWidth

Block Positioning

Blocks on the top section begin from the top edge of the main viewport, while the bottom section begins from the bottom edge. Blocks are dynamically removed from visibility from the midpoint of the viewport. So, a relatively large block number will not draw to the viewport.

Lastly, there can be at most one HUD occupying a block at any time. Trying to position a HUD in an occupied block will result in an error. Keep this in mind when positioning the HUD.

blockSize(bs) string createqueryedit
Sets the height of each block. Available heights are: small, medium and large. In pixel measurements, each corresponds to a 20, 35 or 50 pixel height, respectively.
padding(p) int createqueryedit
Specifies the width of both the left and right margins of a block. Default value is 15 pixels.
blockAlignment(ba) string createqueryedit
Specifies the alignment of the block within its respective column. Available alignments are: "center", "left" and "right". The default alignment is "left".
label(l) string createqueryedit
Text label of the HUD button.
labelFontSize(lfs) string createqueryedit
Sets the font size of the label. Available sizes are: small and large.
buttonWidth(bw) int createqueryedit
Specifies the width of the button.
buttonShape(bsh) string createqueryedit
Specifies the shape of the button. Available button shapes are: "rectangle" and "roundRectangle". The first will draw a rectangular button, while the latter is a rectangle with rounded edges.
pressCommand(pc) script createqueryedit
Specifies the procedure or script to run during a mouse click event.
releaseCommand(rc) script createqueryedit
Specifies the procedure or script to run during a mouse release event.

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 have multiple arguments, passed either as a tuple or a list.

Python examples

import maya.cmds as cmds

# Define a "Hello!" counter procedure. This procedure will output
# "Hello! [number]"
# each time it is run. The number is incremented at the end of each call.
gHelloCount = 0
def HUDButtonHello(*args):
  global gHelloCount
  print 'Hello!( %i )' % gHelloCount
  gHelloCount += 1
# Now create our button. Only execute on mouse release.
cmds.hudButton('HUDHelloButton', s=7, b=5, vis=1, l='Button', bw=80, bsh='roundRectangle', rc=HUDButtonHello )