pymel.core.windows.gradientControlNoAttr

gradientControlNoAttr(*args, **kwargs)

This command creates a control for editing a ramp (2D control curve). The control attaches to an optionVar used to store and retrieve the encoded gradient control points stored in a string.

Flags:

Long name (short name)		Argument Types	Properties
annotation (ann)		unicode
	Annotate the control with an extra string value.
asString (asString)		unicode
	Used to query and set the value of the ramp as a string of comma separated values
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.
changeCommand (cc)		script
	Specifies a command to be executed whenever the value of this ramp is modified. This option should not be used when specifying an optionVar.
currentKey (ck)		int
	Returns the index of the currently selected key.
currentKeyChanged (ckc)		script
	Specifies a command to be executed whenever the selected key changes.
currentKeyColorValue (clv)		float, float, float
	Get or set the color of the currently selected key. Only useful if the ramp is set to be a color ramp.
currentKeyCurveValue (cvv)		bool
	Get or set the value of the currently selected key. Only useful if the ramp is set to be a curve ramp.
currentKeyInterpValue (civ)		int
	Get or set the interpolation value for the current key.
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
	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’”)
dragCommand (dc)		script
	Specifies a command to be executed while the ramp is being modified.Flag can appear in Create mode of commandFlag can have multiple arguments, passed either as a tuple or a list.
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’”)
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
	Enables the background color of the control.
exists (ex)		bool
	Returns true|false depending upon whether the specified object exists. Other flags are ignored.
fullPathName (fpn)		unicode
	Return the full path name of the widget, which includes all the parents
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.
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
	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.
noBackground (nbg)		bool
	Clear/reset the control’s background. Passing true means the background should not be drawn at all, false means the background should be drawn. The state of this flag is inherited by children of this control.
numberOfPopupMenus (npm)		bool
	Return the number of popup menus attached to this control.
optionVar (ov)		unicode
	Specifies the name of the option var used to store and retrieve the string value capturing the curve.
parent (p)		unicode
	The parent layout for this control.
popupMenuArray (pma)		bool
	Return the names of all the popup menus attached to this control.
preventOverride (po)		bool
	If true, this flag disallows overriding the control’s attribute via the control’s right mouse button menu.
rampAsColor (rac)		bool
	Sets whether the ramp should be viewed as a colour ramp or as a curve. Default is as a curve.
useTemplate (ut)		unicode
	Force the command to use a command template other than the current one.
valueAtPoint (vap)		float
	Used during query to specify the point at which to query the curve.
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
	Command that gets executed when visible state of the control changes.
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.

Derived from mel command maya.cmds.gradientControlNoAttr

Example:

import pymel.core as pm

# Create a window with a gradient control for an optionVar
#
pm.window( title='Gradient Control For OptionVar' )
# Result: ui.Window('window1') #
pm.optionVar(stringValueAppend=['falloffCurveOptionVar', '0,1,2'])
pm.optionVar(stringValueAppend=['falloffCurveOptionVar', '1,0,2'])
pm.columnLayout()
# Result: ui.ColumnLayout('window1|columnLayout42') #
pm.gradientControlNoAttr( 'falloffCurve', h=90)
# Result: ui.GradientControlNoAttr('window1|columnLayout42|falloffCurve') #
pm.gradientControlNoAttr( 'falloffCurve', e=True, optionVar='falloffCurveOptionVar' )
# Result: ui.GradientControlNoAttr('window1|columnLayout42|falloffCurve') #
pm.showWindow()

# Query for the value on the curve at a given position.
#
pm.gradientControlNoAttr( 'falloffCurve', q=True, valueAtPoint=0.5 )
# Result: 0.5 #