aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81>2012-05-09 14:01:03 +0000
committerGravatar reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81>2012-05-09 14:01:03 +0000
commita869248bf8fa8d3649b71440d43e7a510f87380b (patch)
tree35cfc66d54ce639adbb701630d0428d928f3cb6f
parent08e791194a9c020b8e2991fff71688c77eeab0bc (diff)
remove obsolete comments
git-svn-id: http://skia.googlecode.com/svn/trunk@3875 2bbb7eff-a529-9590-31e7-b0007b416f81
-rw-r--r--src/core/SkScan_AntiPath.cpp5
1 files changed, 0 insertions, 5 deletions
diff --git a/src/core/SkScan_AntiPath.cpp b/src/core/SkScan_AntiPath.cpp
index 2fed5091c9..2993dc7567 100644
--- a/src/core/SkScan_AntiPath.cpp
+++ b/src/core/SkScan_AntiPath.cpp
@@ -30,10 +30,6 @@
abbreviated with 'i' or 'I' in variable names
- supersampled coordinates, scale equal to the output * SCALE
- NEW_AA is a set of code-changes to try to make both paths produce identical
- results. Its not quite there yet, though the remaining differences may be
- in the subsequent blits, and not in the different masks/runs...
-
SK_USE_EXACT_COVERAGE makes coverage_to_partial_alpha() behave similarly to
coverage_to_exact_alpha(). Enabling it will requrie rebaselining about 1/3
of GMs for changes in the 3 least significant bits along the edges of
@@ -41,7 +37,6 @@
*/
//#define FORCE_SUPERMASK
//#define FORCE_RLE
-//#define SK_SUPPORT_NEW_AA
//#define SK_USE_EXACT_COVERAGE
///////////////////////////////////////////////////////////////////////////////