From f7b4cc602b9a646fbc66f3f17d6bb9c20efc3ead Mon Sep 17 00:00:00 2001 From: jaseg Date: Sun, 24 Jan 2021 18:44:56 +0100 Subject: Initial commit --- .../Documentation/Docs/Overview/FAQ.htm | 104 +++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 upstream/clipper-6.4.2/Documentation/Docs/Overview/FAQ.htm (limited to 'upstream/clipper-6.4.2/Documentation/Docs/Overview/FAQ.htm') diff --git a/upstream/clipper-6.4.2/Documentation/Docs/Overview/FAQ.htm b/upstream/clipper-6.4.2/Documentation/Docs/Overview/FAQ.htm new file mode 100644 index 0000000..91459b9 --- /dev/null +++ b/upstream/clipper-6.4.2/Documentation/Docs/Overview/FAQ.htm @@ -0,0 +1,104 @@ + + + + + + + + + + + + + + + + + + + + FAQ + + + + + + + + + + + + + + + + + + + + + +

FAQ

+ + +

Why does Clipper use integer coordinates, not floats?

+ +

This has been done to preserve numerical robustness. Early versions of the library did use floating point coordinates, but it became apparent that floating point imprecision was always going to cause occasional errors.

+ + +

How do I use floating point coordinates with Clipper?

+ +

It's a simple task to multiply your floating point coordinates by a scaling factor (that's typically a power of 10 depending on the desired precision). Then with the solution paths, divide the returned coordinates by this same scaling factor. Clipper accepts integer coordinates as large as ±4.6e18, so it can accommodate very large scaling.

+ + +

Does Clipper handle polygons with holes?

+ +

'Holes' are defined by the specified polygon filling rule. (See also Clipper.Execute)

+ + +

Some polygons in the solution share a common edge. Is this a bug?

+ +

No, though this should happen rarely as of version 6. (See Clipper.Execute for more about this.)

+ + +

I have lots of polygons that I want to 'union'. Can I do this in one operation?

+ +

Yes. Just add all the polygons as subject polygons to the Clipper object. (You don't have to assign both subject and clip polygons.)

+ + +

The polygons produced by ClipperOffset have tiny artefacts? Could this be a bug?

+ +

Make sure the input polygons don't self-intersect. Tiny self-intersections can sometimes be produced by previous clipping operations. These can be cleaned up using the CleanPolygon and CleanPolygons functions. Also, make sure the supplied polygons don't overlap. If they do, offset these separately. Finally, the precision of the input coordinates may be a problem. Because the Clipper Library only operates on integer coordinates, you may need to scale your coordinates (eg by a factor of 10) to improve precision.

+ + +

Is there an easy way to reverse polygon orientations?

+ +

Yes, see ReversePaths.

+ +

+ + +

My drawings contain lots of beziers, ellipses and arcs. How can I perform clipping operations on these?

+ +

You'll have to convert them to 'flattened' paths. For an example of how this can be done (and even reconstructed back into beziers, arcs etc), see the CurvesDemo application included in this library.

+ + +

FAQ

See Also