Lines Matching full:path
43 * A caller may wish to use a path renderer to draw a path into the stencil buffer. However,
44 * the path renderer itself may require use of the stencil buffer. Also a path renderer may
46 * covered by bounding geometry but outside the path. These exterior pixels would still be
51 * The path is rendered exactly as the draw state indicates including support
54 * 2) kStencilOnly: The path renderer cannot apply arbitrary stencil rules nor shade and stencil
55 * simultaneously. The path renderer does support the stencilPath() function
57 * covered by the path.
58 * 3) kNoSupport: This path renderer cannot be used to stencil the path.
67 * This function is to get the stencil support for a particular path. The path's fill must
68 * not be an inverse type. The path will always be filled and not stroked.
77 kAsBackup, // i.e. This renderer is better than SW fallback if no others can draw the path.
109 * Returns how well this path renderer is able to render the given path. Returning kNo or
110 * kAsBackup allows the caller to keep searching for a better path renderer. This function is
111 * called when searching for the best path renderer to draw a path.
142 * Draws the path into the draw target. If getStencilSupport() would return kNoRestriction then
164 * Draws the path to the stencil buffer. Assume the writable stencil bits are already
165 * initialized to zero. The pixels inside the path will have non-zero stencil values afterwards.
174 // Helper for getting the device bounds of a path. Inverse filled paths will have bounds set
175 // by devSize. Non-inverse path bounds will not necessarily be clipped to devSize.
176 static void GetPathDevBounds(const SkPath& path,