Go to: Synopsis. Return value. Flags. Python examples.
hardenPointCurve(
curve
, [caching=boolean], [constructionHistory=boolean], [multiplicity=int], [name=string], [nodeState=int], [object=boolean], [replaceOriginal=boolean])
Note: Strings representing object names and arguments must be separated by commas. This is not depicted in the synopsis.
hardenPointCurve is undoable, queryable, and editable.
The hardenPointCurve command changes the knots of a curve given a list
of control point indices so that the knot corresponding to that
control point gets the specified multiplicity. Multiplicity of -1 is
the universal value used for multiplicity equal to the degree of
the curve.
limitations
The CV whose multiplicity is being raised needs to have its
neighbouring CVs of multiplicity 1. How many neighbours depends on
the degree of the curve and the difference in CV multiplicities before
and after this operation. For example, if you're changing a CV of
multiplicity 1 into a CV of multiplicity 3, you will need the 4
neighbouring CVs (2 on each side) to be of multiplicity 1. The CVs
that do not satisfy that requirement will be ignored.
| string[] | Object name and node name |
In query mode, return type is based on queried flag.
caching, constructionHistory, multiplicity, name, nodeState, object, replaceOriginal
| Long name (short name) |
Argument types |
Properties |
|
caching(cch)
|
boolean
|
  
|
|
Toggle caching for all attributes so that no recomputation is needed
|
|
multiplicity(m)
|
int
|
|
|
the required multiplicity of the curve knot
Default: -1
|
|
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-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
|
|
| Common flags |
constructionHistory(ch)
|
boolean
|
|
|
Turn the construction history on or off.
|
|
name(n)
|
string
|
|
|
Sets the name of the newly-created node. If it contains
namespace path, the new node will be created under the
specified namespace; if the namespace does not exist, it
will be created.
|
|
object(o)
|
boolean
|
|
|
Create the result, or just the dependency node.
|
|
replaceOriginal(rpo)
|
boolean
|
|
|
Create "in place" (i.e., replace).
|
|
|
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 have multiple arguments, passed either as a tuple or a list.
|
import maya.cmds as cmds
# Make the example curve.
cmds.curve( d=3, p=((-7.253894, 0, 10.835724), (-7.423939, 0, 6.977646), (-7.400778, 0, 2.798971), (-7.458196, 0, -1.524959), (-2.411453, 0, -1.07677), (1.44791, 0, -0.8977448), (5.526346, 0, -0.8610371), (5.740407, 0, 3.780402), (6.293634, 0, 7.571941), (5.957847, 0, 10.72273), (2.753946, 0, 10.894312), (-0.6375988, 0, 11.062571), (-5.889847, 0, 10.940658)), k=(0, 0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 10, 10) )
# Raise the ones that you want to have "sharp" corners
cmds.hardenPointCurve( 'curve1.cv[3]', 'curve1.cv[6]', 'curve1.cv[9]', ch=True, rpo=True, m=-1 )
# Same result, as the in-between CVs are ignored:
cmds.undo()
cmds.hardenPointCurve( 'curve1.cv[0:12]', ch=1, rpo=1, m=-1 )