This command creates a context which may be used to move keyframes within the graph editor
Long name (short name) | Argument Types | Properties | |
---|---|---|---|
exists (ex) | bool | ||
|
|||
history (ch) | bool | ||
|
|||
image1 (i1) | unicode | ||
image2 (i2) | unicode | ||
image3 (i3) | unicode | ||
|
|||
moveFunction (mf) | unicode | ||
linear | power | constant. Specifies how the keys are dragged. The default move type is constant where all keys move the same amount as controlled by user movement. Power provides a fall-off function where the center of the drag moves the most and the keys around the drag move less.Flag can appear in Create mode of commandFlag can have multiple arguments, passed either as a tuple or a list. |
|||
name (n) | unicode | ||
|
|||
option (o) | unicode | ||
Valid values are “move,” “insert,” “over,” and “segmentOver.” When you “move” a key, the key will not cross over (in time) any keys before or after it. When you “insert” a key, all keys before or after (depending upon the -timeChange value) will be moved an equivalent amount. When you “over” a key, the key is allowed to move to any time (as long as a key is not there already). When you “segmentOver” a set of keys (this option only has a noticeable effect when more than one key is being moved) the first key (in time) and last key define a segment (unless you specify a time range). That segment is then allowed to move over other keys, and keys will be moved to make room for the segment. |
Derived from mel command maya.cmds.moveKeyCtx
Example:
import pymel.core as pm
import maya.cmds as cmds
# Create a move key context which works in insert mode
# for the graph editor
#
newCtx = pm.moveKeyCtx(option='insert')
# Edit the context to over mode
#
pm.moveKeyCtx( newCtx, e=True, option='over' )
# Result: u'moveKeyCtx1' #