diff options
author | reed@android.com <reed@android.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2009-04-02 16:59:40 +0000 |
---|---|---|
committer | reed@android.com <reed@android.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2009-04-02 16:59:40 +0000 |
commit | 80e39a77b16f4396eed230efea1d0b2fc8cbfb00 (patch) | |
tree | 01d340ffe7692fd0d7271b9fd30e151574b1b7e8 /tests/SrcOverTest.cpp | |
parent | 57b799e951064b9328b5c676dcc3b4cb4477cc2b (diff) |
cleanup formating (e.g. no trailing spaces)
git-svn-id: http://skia.googlecode.com/svn/trunk@143 2bbb7eff-a529-9590-31e7-b0007b416f81
Diffstat (limited to 'tests/SrcOverTest.cpp')
-rw-r--r-- | tests/SrcOverTest.cpp | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/tests/SrcOverTest.cpp b/tests/SrcOverTest.cpp index cf429de48e..497b3a81e1 100644 --- a/tests/SrcOverTest.cpp +++ b/tests/SrcOverTest.cpp @@ -21,7 +21,7 @@ static void test_srcover_hack(skiatest::Reporter* reporter) { /* Here's the idea. Can we ensure that when we blend on top of an opaque dst, that the result always stay's opaque (i.e. exactly 255)? */ - + unsigned i; int opaqueCounter0 = 0; int opaqueCounter1 = 0; @@ -42,7 +42,7 @@ static void test_srcover_hack(skiatest::Reporter* reporter) { REPORTER_ASSERT(reporter, opaqueCounter0 == 129); REPORTER_ASSERT(reporter, opaqueCounter1 == 256); REPORTER_ASSERT(reporter, opaqueCounter2 == 256); - + // Now ensure that we never over/underflow a byte for (i = 0; i <= 255; i++) { for (unsigned dst = 0; dst <= 255; dst++) { @@ -56,11 +56,12 @@ static void test_srcover_hack(skiatest::Reporter* reporter) { } REPORTER_ASSERT(reporter, r1 <= 255 && r1 >= max); REPORTER_ASSERT(reporter, r2 <= 255 && r2 >= max); - + #if 0 // this shows where r1 (faster) differs from r2 (more exact) if (r1 != r2) { - SkDebugf("--- dst=%d i=%d r1=%d r2=%d exact=%g\n", dst, i, r1, r2, i + dst - dst*i/255.0f); + SkDebugf("--- dst=%d i=%d r1=%d r2=%d exact=%g\n", + dst, i, r1, r2, i + dst - dst*i/255.0f); } #endif } |