pymel.core.context.polyMergeEdgeCtx¶

polyMergeEdgeCtx(*args, **kwargs)¶

Sews two border edges together.The new edge is located either on the first, last, or between both selected edges, depending on the mode. Both edges must belong to the same object, and orientations must match (i.e. normals on corresponding faces must point in the same direction).Edge flags are mandatory. Create a new context to merge edges on polygonal objects

Flags:

Long Name / Short Name		Argument Types	Properties
activeNodes / anq		bool
	Return the active nodes in the tool
caching / cch		bool
	Toggle caching for all attributes so that no recomputation is needed
constructionHistory / ch		bool
	Turn the construction history on or off (where applicable). If construction history is on then the corresponding node will be inserted into the history chain for the mesh. If construction history is off then the operation will be performed directly on the object. Note:If the object already has construction history then this flag is ignored and the node will always be inserted into the history chain.
exists / ex		bool
	Returns true or false depending upon whether the specified object exists. Other flags are ignored.
firstEdge / fe		int
	First edge to merge. Invalid default value to force the value to be set. Default:-1
frozen / fzn		bool
image1 / i1		unicode
	First of three possible icons representing the tool associated with the context.
image2 / i2		unicode
	Second of three possible icons representing the tool associated with the context.
image3 / i3		unicode
	Third of three possible icons representing the tool associated with the context.
immediate / im		bool
	Acts on the object not the tool defaults
mergeMode / mm		int
	Merge mode : 0=first, 1=halfway between both edges, 2=second. Default:1
mergeTexture / mt		bool
	Boolean which is used to decide if uv coordinates should be merged or not - along with the geometry. Default:false
name / n		unicode
	If this is a tool command, name the tool appropriately.
nodeState / nds		int
	Maya dependency nodes have 6 possible states. The Normal (0), HasNoEffect (1), and Blocking (2)states can be used to alter how the graph is evaluated. The Waiting-Normal (3), Waiting-HasNoEffect (4), Waiting-Blocking (5)are for internal use only. They temporarily shut off parts of the graph during interaction (e.g., manipulation). The understanding is that once the operation is done, the state will be reset appropriately, e.g. Waiting-Blockingwill reset back to Blocking. The Normaland Blockingcases apply to all nodes, while HasNoEffectis node specific; many nodes do not support this option. Plug-ins store state in the MPxNode::stateattribute. Anyone can set it or check this attribute. Additional details about each of these 3 states follow. StateDescriptionNormalThe normal node state. This is the default.HasNoEffectThe HasNoEffectoption (a.k.a. pass-through), is used in cases where there is an operation on an input producing an output of the same data type. Nearly all deformers support this state, as do a few other nodes. As stated earlier, it is not supported by all nodes. Its typical to implement support for the HasNoEffectstate in the nodes compute method and to perform appropriate operations. Plug-ins can also support HasNoEffect. The usual implementation of this state is to copy the input directly to the matching output without applying the algorithm in the node. For deformers, applying this state leaves the input geometry undeformed on the output. BlockingThis is implemented in the depend node base class and applies to all nodes. Blockingis applied during the evaluation phase to connections. An evaluation request to a blocked connection will return as failures, causing the destination plug to retain its current value. Dirty propagation is indirectly affected by this state since blocked connections are never cleaned. When a node is set to Blockingthe behavior is supposed to be the same as if all outgoing connections were broken. As long as nobody requests evaluation of the blocked node directly it wont evaluate after that. Note that a blocked node will still respond to getAttrrequests but a getAttron a downstream node will not reevaluate the blocked node. Setting the root transform of a hierarchy to Blockingwont automatically influence child transforms in the hierarchy. To do this, youd need to explicitly set all child nodes to the Blockingstate. For example, to set all child transforms to Blocking, you could use the following script. import maya.cmds as cmds def blockTree(root): nodesToBlock = [] for node in {child:1 for child in cmds.listRelatives( root, path=True, allDescendents=True )}.keys(): nodesToBlock += cmds.listConnections(node, source=True, destination=True ) for node in {source:1 for source in nodesToBlock}.keys(): cmds.setAttr( ‘%s.nodeState’ % node, 2 ) Applying this script would continue to draw objects but things would not be animated. Default:kdnNormal
previous / pv		bool
	Reset to previously stored values
reset / rs		bool
	Reset to default values
secondEdge / se		int
	Second edge to merge. Invalid default value to force the value to be set. Default:-1 Flag can have multiple arguments, passed either as a tuple or a list.
toolNode / tnq		bool
	Return the node used for tool defaults Common poly modifier operation flags

Derived from mel command maya.cmds.polyMergeEdgeCtx

Example:

import pymel.core as pm

# Create a poly plane
pm.polyPlane(w=10, h=10, sx=10, sy=10, n='pPlane1')

# Create a new poly merge edge context, set to use first selected edge as the new edge, then switch to it
pm.polyMergeEdgeCtx('polyMergeEdgeCtx1', mm=0)
pm.setToolTo('polyMergeEdgeCtx1')