Self._cached_tc_offset = actualframe - self.pro_audio.timecode_to_frame(relativeTC) RelativeTC = self.pro_audio.Timecode(selectedNode).getTimecode_from_node() Raise IOError('selected Audio node is NOT a Bwav so can't be used as reference') Label='frame %s = %s' % (reference.startFrame,reference.bwav_timecodeFormatted())) Log.warning('Please only select 1 piece of Audio to use for reference') SelectedAudio=cmds.ls(sl=True, type='audio') If you pass it a node, and that node has the timecode attrs, then it caches the offset itself. If you pass this a bwav then it caches that bwav for use as the offset. : PRO_PACK : set the internal reference offset used to offset the audionode. R_bc = cmds.createNode('blendColors', name='%s_rotate_bc' % driven)Д¬mds.connectAttr('%s.rotate' % targ2, '%s.color1' % r_bc)Д¬mds.connectAttr('%s.rotate' % targ1, '%s.color2' % r_bc)Д¬mds.connectAttr(blendAttr, '%s.blender' % r_bc)Д¬mds.connectAttr('%s.output' % r_bc, '%s.rotate' % driven)Дef _uicb_setReferenceBwavNode(self, *args): T_bc = cmds.createNode('blendColors', name='%s_translate_bc' % driven)Д¬mds.connectAttr('%s.t' % targ2, '%s.color1' % t_bc)Д¬mds.connectAttr('%s.t' % targ1, '%s.color2' % t_bc)Д¬mds.connectAttr(blendAttr, '%s.blender' % t_bc)Д¬mds.connectAttr('%s.output' % t_bc, '%s.t' % driven) Return showDialog( 'Argument Error', 'Please supply or select targ1, targ2 and driven nodes' ) If not targ1 and not targ2 and not driven: If a blendAttr is supplied, this is connected to the blender value Sets up blending of translation / rotation values from targs 1 & 2 on the driven node. With callback functions, you get an error message if your callback does not take the correct number of arguments.Def blendAttrs(targ1=None, targ2=None, driven=None, blendAttr=None, translate=1, rotate=1): The second style of Python callback uses a compiled function, where Maya passes the values as arguments to the function: You provide the format string and the UI element provides the dictionary for the format operation.) The floatSlider command formats the string with the current slider value before executing the script. (The dictionary is applied to the string later, before it is executed. The format operation is passed a dictionary of items for the substitution where the names of the values are 1, 2, and so on. However, PythonвЂ™s format operator is used to do the substitutions.

If the callback is a string which is to be evaluated, then Maya does string substitution as in MEL. The value of the float slider is substituted for this positional argument when the callback is run.ДЇor Python, two different ways of substituting values from controls in callbacks are supported. For example, the callback MEL script for a float slider control could contain #1. Positional arguments refer to the arguments that UI elements pass to their callback scripts. Python: skinCluster (q=True, inf='joint1', dr=True) Query where a flag/argument does not take a value Query where a flag/argument takes a value MEL: move -objectSpace 2.0 1.0 1.0 nurbsSphere1 The same as MEL except arguments must come first (You can also use a tuple or tuples, a list of lists, or a tuple of lists.) Use a list to hold the multiple flag values MEL: ls -type nurbsSurface -type transform Use a tuple to specify multiple arguments All old flags have been left in place.ДЇlags with no arguments get a boolean True/False switch

In all cases, the flags are backwards compatible. The use of all of these flags is documented in the CommandsPython reference documentation.

roundConstantRadius : a new side flag replaces the use of sidea and sideb that are supposed to be intermixed.

polењњreateFacet : the existing point flag as been modified so that it may be also used to specify holes.

polySplit : new insertpoint flag which can be used in place of the facepoint and edgepoint flags.

polyAppend : new append flag which can be used in place of the point, edge, and hole flags.

polyAppendVertex : new append flag which can be used in place of the point, vertex, and hole flags.

The few commands which relied on this have been extended so that a single multi-use flag handles the job of the individual multi-use flags. Since each multi-use flagвЂ™s arguments are provided in a separate list in Python, there is no way to intermix them. This causes a problem for commands in which different multi-use flags must be mixed-and-matched. Certain flag changes to Maya commands are necessary because the arguments for multi-use flags in Python must be passed as a list to the flag.

Maya python ls