History log of /external/skia/tests/TessellatingPathRendererTests.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
d309e7aa0efa2d5dd7e7b1af97026fcd3a047e98 30-Apr-2015 bsalomon <bsalomon@google.com> This replaces the texture creation/caching functions on GrContext with a GrTextureProvider interface. The goal is to pass this narrowly focused object in places that currently take a GrContext but don't need and shouldn't use its other methods. It also has an extended private interface for interacting with non-texture resource types.

Review URL: https://codereview.chromium.org/1107973004
/external/skia/tests/TessellatingPathRendererTests.cpp
1899651ffc459f5462aa989cd6d08507947b67e4 27-Apr-2015 kkinnunen <kkinnunen@nvidia.com> Extract gpu line dashing to GrDashLinePathRenderer

Move line dashing logic from GrContext::drawPath to
GrDashLinePathRenderer. This makes it possible to let path renderers render arbitrary dashed paths.

End goal is to implement dashing in GrStencilAndCoverPathRenderer.

Review URL: https://codereview.chromium.org/1100073003
/external/skia/tests/TessellatingPathRendererTests.cpp
c8e934007a48465e584cdeed9ef02077d3cd5451 21-Apr-2015 senorblanco <senorblanco@chromium.org> Yet more ASAN fixes.

More nullptr checks for factories I have added.
Other checks more Yoda-like I have made. (Skia style this is.)

BUG=skia:

Review URL: https://codereview.chromium.org/1086393004
/external/skia/tests/TessellatingPathRendererTests.cpp
0e95b116fcc7bec1bbdf5f0459ebd464c458f714 21-Apr-2015 senorblanco <senorblanco@chromium.org> Speculative fix for ASAN build.

Check for NULL GrContext in TessellatingPathRendererTests.
Also fix an upload nag (no #includes before GPU #ifdef).

TBR=bsalomon@google.com

Review URL: https://codereview.chromium.org/1097943004
/external/skia/tests/TessellatingPathRendererTests.cpp
a2b6d28755916cbb4817cd9d1cd1b0e237de9a50 02-Mar-2015 senorblanco <senorblanco@chromium.org> Fix for out-of-bounds intersection (found by fuzzer).

Sometimes, the intersection returned by check_intersection() is
out-of-bounds for both edges (above both tops or below both bottoms)
due to floating-point inaccuracy. This causes split_edge() to create a
tiny negative-length edge on one side (which would then assert).
Although we could safely remove this assert and allow the negative
length edge to be removed, it's faster/safer to simply avoid its
creation in the first place by adjusting one edge to the other edge's
endpoint.

Added a new unit test to exercise this case.

Review URL: https://codereview.chromium.org/968993002
/external/skia/tests/TessellatingPathRendererTests.cpp
d6ed19cc751463285491a538bc7bf154cc7e6d8c 26-Feb-2015 senorblanco <senorblanco@chromium.org> Tessellating GPU path renderer.

This path renderer converts paths to linear contours, resolves intersections via Bentley-Ottman, implements a trapezoidal decomposition a la Fournier and Montuno to produce triangles, and renders those with a single draw call. It does not currently do antialiasing, so it must be used in conjunction with multisampling.

A fair amount of the code is to handle floating point edge cases in intersections. Rather than perform exact computations (which would require arbitrary precision arithmetic), we reconnect the mesh to reflect the intersection points. For example, intersections can occur above the current vertex, and force edges to be merged into the current vertex, requiring a restart of the intersections. Splitting edges for intersections can also force them to merge with formerly-distinct edges in the same polygon, or to violate the ordering of the active edge list, or the active edge state of split edges.

BUG=skia:

Review URL: https://codereview.chromium.org/855513004
/external/skia/tests/TessellatingPathRendererTests.cpp