/* * Copyright 2006 The Android Open Source Project * * Use of this source code is governed by a BSD-style license that can be * found in the LICENSE file. */ #ifndef SkPath_DEFINED #define SkPath_DEFINED #include "include/core/SkMatrix.h" #include "include/core/SkPathTypes.h" #include "include/core/SkPoint.h" #include "include/core/SkRect.h" #include "include/core/SkRefCnt.h" #include "include/core/SkScalar.h" #include "include/core/SkTypes.h" #include "include/private/base/SkDebug.h" #include "include/private/base/SkTo.h" #include "include/private/base/SkTypeTraits.h" #include <atomic> #include <cstddef> #include <cstdint> #include <initializer_list> #include <tuple> #include <type_traits> class SkData; class SkPathRef; class SkRRect; class SkWStream; enum class SkPathConvexity; enum class SkPathFirstDirection; struct SkPathVerbAnalysis; // WIP -- define this locally, and fix call-sites to use SkPathBuilder (skbug.com/9000) //#define SK_HIDE_PATH_EDIT_METHODS /** \class SkPath SkPath contain geometry. SkPath may be empty, or contain one or more verbs that outline a figure. SkPath always starts with a move verb to a Cartesian coordinate, and may be followed by additional verbs that add lines or curves. Adding a close verb makes the geometry into a continuous loop, a closed contour. SkPath may contain any number of contours, each beginning with a move verb. SkPath contours may contain only a move verb, or may also contain lines, quadratic beziers, conics, and cubic beziers. SkPath contours may be open or closed. When used to draw a filled area, SkPath describes whether the fill is inside or outside the geometry. SkPath also describes the winding rule used to fill overlapping contours. Internally, SkPath lazily computes metrics likes bounds and convexity. Call SkPath::updateBoundsCache to make SkPath thread safe. */ class SK_API SkPath { … }; #endif