pymel.core.modeling.polyBridgeEdge¶
- polyBridgeEdge(*args, **kwargs)¶
Bridges two sets of edges.
Flags:
Long Name / Short Name Argument Types Properties bridgeOffset / bo int Add offset to which vertices are connected. Default:0 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. curveType / ctp int Format: 0 - Linear, 1 - Blend, 2 - Curve Default:TdnpolyBridgeEdge::Linear direction / d int divisions / dv int The number of subdivisions in the bridging faces (resulting in (divisions+1) row of faces). Default:1 frozen / fzn bool inputCurve / inc PyNode This flag specifies the name of the curve to be used as input for the operation. name / n unicode Give a name to the resulting node. 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 reverse / rev bool smoothingAngle / sma float Angle below which new edges will be smoothed Default:kPi/6.0 sourceDirection / sd int startVert1 / sv1 int The start vertex from the first set of edges Default:-1 startVert2 / sv2 int The start vertex from the second set of edges Default:-1 taper / tp float Taper or Scale along the extrusion path Default:1.0 taperCurve_FloatValue / cfv float Value for taperCurve; Curve control for taper along extrusion Using this curve, the taper along extrusion can be changed from a simple linear scaling to custom scaling along the extrusion path. taperCurve_Interp / ci int Interpolation type for taperCurve; Curve control for taper along extrusion Using this curve, the taper along extrusion can be changed from a simple linear scaling to custom scaling along the extrusion path. taperCurve_Position / cp float Position for taperCurve; Curve control for taper along extrusion Using this curve, the taper along extrusion can be changed from a simple linear scaling to custom scaling along the extrusion path. targetDirection / td int twist / twt float Twist or Rotation along the extrusion path Default:0.0 worldSpace / ws bool This flag specifies which reference to use. If on: all geometrical values are taken in world reference. If off: all geometrical values are taken in object reference. C: Default is off. Q: When queried, this flag returns an int. Flag can have multiple arguments, passed either as a tuple or a list. Derived from mel command maya.cmds.polyBridgeEdge
Example:
import pymel.core as pm pm.file( f=True, new=True ) pm.polyCube( sx=3, sy=3, sz=3 ) pm.delete( 'pCube1.f[9:17]' ) pm.move( -2, 0, 0, r=True ) pm.rotate( 0, 0, -90, r=True, os=True ) pm.polyCube( sx=3, sy=3, sz=3 ) pm.delete( 'pCube2.f[9:17]' ) pm.move( 2, 0, 0, r=True ) pm.rotate( 0, 0, 90, r=True, os=True ) pm.polyUnite( 'pCube1', 'pCube2', ch=1 ) # Now bridge the two sets of border edges pm.polyBridgeEdge( 'polySurface1.e[9:14]', 'polySurface1.e[42:47]', 'polySurface1.e[105:110]', 'polySurface1.e[138:143]', sv1=12, sv2=67, divisions=10 )