aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/gpu/GrPathProcessor.h
diff options
context:
space:
mode:
authorGravatar Brian Salomon <bsalomon@google.com>2018-06-06 17:16:05 -0400
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2018-06-06 21:56:24 +0000
commit969bdef64139c417f5c0b8f2fbf2638bb9d7dc95 (patch)
treefb59076e70b44760382842b574dd4e132cbc25e6 /src/gpu/GrPathProcessor.h
parent7db95a645147b7fef47647dc5d3df32b05b141d9 (diff)
Remove GrGeometryProcessor knowledge of explicit local coords
This seems to be part of an older model where the base class was more aware of how subclasses handled local coords. Only the default geometry processor uses it and it already incorporates the existence of explicit local coords into its shader key. Other GPs that used explicit local coords don't use this. Change-Id: Ia396f2a5e626e57470905ae770f1576386c0cefb Reviewed-on: https://skia-review.googlesource.com/132665 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Brian Osman <brianosman@google.com> Auto-Submit: Brian Salomon <bsalomon@google.com>
Diffstat (limited to 'src/gpu/GrPathProcessor.h')
-rw-r--r--src/gpu/GrPathProcessor.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/gpu/GrPathProcessor.h b/src/gpu/GrPathProcessor.h
index 581bd5052f..72e5168a4f 100644
--- a/src/gpu/GrPathProcessor.h
+++ b/src/gpu/GrPathProcessor.h
@@ -40,8 +40,6 @@ public:
private:
GrPathProcessor(GrColor, const SkMatrix& viewMatrix, const SkMatrix& localMatrix);
- bool hasExplicitLocalCoords() const override { return false; }
-
GrColor fColor;
const SkMatrix fViewMatrix;
const SkMatrix fLocalMatrix;