Memory-managed wrapper type.

Returns whether two paths have identical structure.

Note that it is possible to construct paths that render identical even though they don't have the same structure.

Since: 4.22

Calls func for every operation of the path.

Note that this may only approximate self, because paths can contain optimizations for various specialized contours, and depending on the flags, the path may be decomposed into simpler curves than the ones that it contained originally.

This function serves two purposes:

• When the flags allow everything, it provides access to the raw, unmodified data of the path.
• When the flags disallow certain operations, it provides an approximation of the path using just the allowed operations.

Since: 4.14

Finds intersections between two paths.

This function finds intersections between path1 and path2, and calls func for each of them, in increasing order for path1.

If path2 is not provided or equal to path1, the function finds non-trivial self-intersections of path1.

When segments of the paths coincide, the callback is called once for the start of the segment, with gSKPATHINTERSECTIONSTART, and once for the end of the segment, with gSKPATHINTERSECTIONEND. Note that other intersections may occur between the start and end of such a segment.

If func returns FALSE, the iteration is stopped.

Since: 4.20

Computes the bounds of the given path.

The returned bounds may be larger than necessary, because this function aims to be fast, not accurate. The bounds are guaranteed to contain the path. For accurate bounds, use pathGetTightBounds.

It is possible that the returned rectangle has 0 width and/or height. This can happen when the path only describes a point or an axis-aligned line.

If the path is empty, false is returned and bounds are set to rectZero. This is different from the case where the path is a single point at the origin, where the bounds will also be set to the zero rectangle but true will be returned.

Since: 4.14

Computes the bounds for stroking the given path with the given parameters.

The returned bounds may be larger than necessary, because this function aims to be fast, not accurate. The bounds are guaranteed to contain the area affected by the stroke, including protrusions like miters.

Since: 4.14

Computes the tight bounds of the given path.

This function works harder than pathGetBounds to produce the smallest possible bounds.

Since: 4.22

Returns whether a point is inside the fill area of a path.

Note that this function assumes that filling a contour implicitly closes it.

Since: 4.14

Returns if the path represents a single closed contour.

Since: 4.14

Checks if the path is empty, i.e. contains no lines or curves.

Since: 4.14

Constructs a path from a serialized form.

The string is expected to be in (a superset of) SVG path syntax, as e.g. produced by pathToString.

A high-level summary of the syntax:

• M x y Move to (x, y)
• L x y Add a line from the current point to (x, y)
• Q x1 y1 x2 y2 Add a quadratic Bézier from the current point to (x2, y2), with control point (x1, y1)
• C x1 y1 x2 y2 x3 y3 Add a cubic Bézier from the current point to (x3, y3), with control points (x1, y1) and (x2, y2)
• Z Close the contour by drawing a line back to the start point
• H x Add a horizontal line from the current point to the given x value
• V y Add a vertical line from the current point to the given y value
• T x2 y2 Add a quadratic Bézier, using the reflection of the previous segments' control point as control point
• S x2 y2 x3 y3 Add a cubic Bézier, using the reflection of the previous segments' second control point as first control point
• A rx ry r l s x y Add an elliptical arc from the current point to (x, y) with radii rx and ry. See the SVG documentation for how the other parameters influence the arc.
• O x1 y1 x2 y2 w Add a rational quadratic Bézier from the current point to (x2, y2) with control point (x1, y1) and weight w.

All the commands have lowercase variants that interpret coordinates relative to the current point.

The O command is an extension that is not supported in SVG.

Since: 4.14

Converts the path into a human-readable representation.

The string is compatible with (a superset of) SVG path syntax, see pathParse for a summary of the syntax.

Since: 4.14

Increases the reference count of a path by one.

Since: 4.14

Appends the path to a cairo context for drawing with Cairo.

This may cause some suboptimal conversions to be performed as Cairo does not support all features of GskPath.

This function does not clear the existing Cairo path. Call cairo_new_path() if you want this.

Since: 4.14

Converts the path into a human-readable string.

You can use this function in a debugger to get a quick overview of the path.

This is a wrapper around pathPrint, see that function for details.

Since: 4.14

Decreases the reference count of a path by one.

If the resulting reference count is zero, frees the path.

Since: 4.14