Nope, thanks for the thought
I have this without declaring it a list
Code: Select all
myIPOCurveX = ((H1_X, 0, 0, P_X, 0, 0, H2_X, 0, 0)) # currently redundant
myIPOCurveY = ((0, H1_Y, 0, 0, P_Y, 0, 0, H2_Y, 0)) # currently redundant
myIPOCurveZ = ((0, 0, H1_Z, 0, 0, P_Z, 0, 0, H2_Z)) # currently redundant
But after days of scouring I found it, hidden in an obscure piece of documentation
Code: Select all
def setBeztriple(curvepos,pointpos,newbeztriple):
"""
Sets the beztriple of the Ipo (B{deprecated}). B{Note}: use
L{IpoCurve.bezierPoints<IpoCurve.IpoCurve.bezierPoints>} to get a
BezTriple point, then use the
L{BezTriple} API to set the point's attributes.
@type curvepos: int
@param curvepos: the position of the curve in the Ipo.
@type pointpos: int
@param pointpos: the position of the point in the curve.
@type newbeztriple: list of 9 floats
@param newbeztriple: the new value for the point
@rtype: None
@return: None
"""
Its one of those areas that you always skip over because ots either no longer maintained or is due to be removed entirely
Yet it leaves me with another problem, deciphering
L{IpoCurve.bezierPoints<IpoCurve.IpoCurve.bezierPoints>} to get a
BezTriple point, then use the
L{BezTriple} API to set the point's attributes
to work with my needs