Adds a point to a curve, at "position", with control points "in" and "out".
If "at_position" is given, the point is inserted before the point number "at_position", moving that point (and every point after) after the inserted point. If "at_position" is not given, or is an illegal value (at_position <0 or at_position >= [method get_point_count]), the point will be appended at the end of the point list.
Returns the total length of the curve, based on the cached points. Given enough density (see [method set_bake_interval]), it should be approximate enough.
</description>
</method>
<methodname="get_baked_points"qualifiers="const">
<returntype="PoolVector2Array">
</return>
<description>
Returns the cache of points as a [PoolVector2Array].
</description>
</method>
<methodname="get_point_count"qualifiers="const">
<returntype="int">
</return>
<description>
Returns the number of points describing the curve.
</description>
</method>
<methodname="get_point_in"qualifiers="const">
<returntype="Vector2">
</return>
<argumentindex="0"name="idx"type="int">
</argument>
<description>
Returns the position of the control point leading to the vertex "idx". If the index is out of bounds, the function sends an error to the console, and returns (0, 0).
</description>
</method>
<methodname="get_point_out"qualifiers="const">
<returntype="Vector2">
</return>
<argumentindex="0"name="idx"type="int">
</argument>
<description>
Returns the position of the control point leading out of the vertex "idx". If the index is out of bounds, the function sends an error to the console, and returns (0, 0).
Returns the position of the vertex "idx". If the index is out of bounds, the function sends an error to the console, and returns (0, 0).
</description>
</method>
<methodname="interpolate"qualifiers="const">
<returntype="Vector2">
</return>
<argumentindex="0"name="idx"type="int">
</argument>
<argumentindex="1"name="t"type="float">
</argument>
<description>
Returns the position between the vertex "idx" and the vertex "idx"+1, where "t" controls if the point is the first vertex (t = 0.0), the last vertex (t = 1.0), or in between. Values of "t" outside the range (0.0 >= t <=1) give strange, but predictable results.
If "idx" is out of bounds it is truncated to the first or last vertex, and "t" is ignored. If the curve has no points, the function sends an error to the console, and returns (0, 0).
Returns a point within the curve at position "offset", where "offset" is measured as a pixel distance along the curve.
To do that, it finds the two cached points where the "offset" lies between, then interpolates the values. This interpolation is cubic if "cubic" is set to true, or linear if set to false.
Cubic interpolation tends to follow the curves better, but linear is faster (and often, precise enough).
</description>
</method>
<methodname="interpolatef"qualifiers="const">
<returntype="Vector2">
</return>
<argumentindex="0"name="fofs"type="float">
</argument>
<description>
Returns the position at the vertex "fofs". It calls [method interpolate] using the integer part of fofs as "idx", and its fractional part as "t".
</description>
</method>
<methodname="remove_point">
<returntype="void">
</return>
<argumentindex="0"name="idx"type="int">
</argument>
<description>
Deletes the point "idx" from the curve. Sends an error to the console if "idx" is out of bounds.
Returns a list of points along the curve, with a curvature controlled point density. That is, the curvier parts will have more points than the straighter parts.
This approximation makes straight segments between each point, then subdivides those segments until the resulting shape is similar enough.
"max_stages" controls how many subdivisions a curve segment may face before it is considered approximate enough. Each subdivision splits the segment in half, so the default 5 stages may mean up to 32 subdivisions per curve segment. Increase with care!
"tolerance_degrees" controls how many degrees the midpoint of a segment may deviate from the real curve, before the segment has to be subdivided.
The distance in pixels between two adjacent cached points. Changing it forces the cache to be recomputed the next time the [method get_baked_points] or [method get_baked_length] function is called. The smaller the distance, the more points in the cache and the more memory it will consume, so use with care.