Go to: Synopsis. Return value. Related. Flags. MEL examples.

Synopsis

polyMergeEdgeCtx [-activeNodes] [-caching boolean] [-constructionHistory boolean] [-exists] [-firstEdge int] [-image1 string] [-image2 string] [-image3 string] [-immediate] [-mergeMode int] [-mergeTexture boolean] [-name string] [-nodeState int] [-previous] [-reset] [-secondEdge int] [-toolNode]

polyMergeEdgeCtx is undoable, queryable, and editable.

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

Return value

stringThe node name.

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

Related

polyCloseBorder, polyCollapseEdge, polyCollapseFacet, polyDelEdge, polyDelFacet, polyDelVertex, polyMergeFacet, polyMergeVertex, polyQuad, polyReduce, polySewEdge

Flags

activeNodes, caching, constructionHistory, exists, firstEdge, image1, image2, image3, immediate, mergeMode, mergeTexture, name, nodeState, previous, reset, secondEdge, toolNode
Long name (short name) Argument types Properties
-activeNodes(-anq) query
Return the active nodes in the tool
-exists(-ex) create
Returns true or false depending upon whether the specified object exists. Other flags are ignored.
-image1(-i1) string createqueryedit
First of three possible icons representing the tool associated with the context.
-image2(-i2) string createqueryedit
Second of three possible icons representing the tool associated with the context.
-image3(-i3) string createqueryedit
Third of three possible icons representing the tool associated with the context.
-immediate(-im) edit
Acts on the object not the tool defaults
-name(-n) string create
If this is a tool command, name the tool appropriately.
-previous(-pv) edit
Reset to previously stored values
-reset(-rs) edit
Reset to default values
-toolNode(-tnq) query
Return the node used for tool defaults
Common poly modifier operation flags
-caching(-cch) boolean createqueryedit
Toggle caching for all attributes so that no recomputation is needed
-constructionHistory(-ch) boolean createquery
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.
-firstEdge(-fe) int createqueryedit
First edge to merge. Invalid default value to force the value to be set.
Default: -1
-mergeMode(-mm) int createqueryedit
Merge mode : 0=first, 1=halfway between both edges, 2=second.
Default: 1
-mergeTexture(-mt) boolean createqueryedit
Boolean which is used to decide if uv coordinates should be merged or not - along with the geometry.
Default: false
-nodeState(-nds) int createqueryedit

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-Blocking will reset back to Blocking.

The Normal and Blocking cases apply to all nodes, while HasNoEffect is node specific; many nodes do not support this option. Plug-ins store state in the MPxNode::state attribute. Anyone can set it or check this attribute. Additional details about each of these 3 states follow.

State Description
Normal The normal node state. This is the default.
HasNoEffect

The HasNoEffect option (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.

It’s typical to implement support for the HasNoEffect state in the node’s 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.

Blocking

This is implemented in the depend node base class and applies to all nodes. Blocking is 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 Blocking the 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 won’t evaluate after that. Note that a blocked node will still respond to getAttr requests but a getAttr on a downstream node will not reevaluate the blocked node.

Setting the root transform of a hierarchy to Blocking won’t automatically influence child transforms in the hierarchy. To do this, you’d need to explicitly set all child nodes to the Blocking state.

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
-secondEdge(-se) int createqueryedit
Second edge to merge. Invalid default value to force the value to be set.
Default: -1

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 be used more than once in a command.

MEL examples

polyPlane -sx 3 -sy 3 -n plg1; move -2 0 0 plg1; delete plg1.f[3:5];
polyPlane -sx 3 -sy 3 -n plg2; delete plg2.f[3:5];
polyPlane -sx 3 -sy 3 -n plg3; move 2 0 0 plg3; delete plg3.f[3:5];

// First
polyMergeEdge -mm 0 -fe 8 -se 12 plg1;

// Between
polyMergeEdge -mm 1 -fe 8 -se 12 plg2;

// Last
polyMergeEdge -mm 2 -fe 8 -se 12 plg3;

// Create a poly plane
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
polyMergeEdgeCtx -mm 0 polyMergeEdgeCtx1;
setToolTo polyMergeEdgeCtx1;