diff options
| author |  bsalomon@google.com <bsalomon@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2011-09-28 15:05:33 +0000 |
|---|---|---|
| committer | bsalomon@google.com <bsalomon@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | 2011-09-28 15:05:33 +0000 |
| commit | 950d7a8d8def14efc98d12d6947347fde351b737 (patch) | |
| tree | d0a12bbf13162fafc04e25e6d185a08b37205aa5 | |
| parent | 8b5abeca877b2d6cb474ce85ed44fcef8e3f2508 (diff) | |
Turn off AA when coverage can't be handled correctly.
This may make some gms go red if bots don't have dual source blend. Will rebase if so.
Review URL: http://codereview.appspot.com/5146049/
git-svn-id: http://skia.googlecode.com/svn/trunk@2347 2bbb7eff-a529-9590-31e7-b0007b416f81
| -rw-r--r-- | gpu/src/GrContext.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gpu/src/GrContext.cpp b/gpu/src/GrContext.cpp index 23ad9e1fce..6aaa28bb92 100644 --- a/gpu/src/GrContext.cpp +++ b/gpu/src/GrContext.cpp @@ -31,7 +31,7 @@ // When we're using coverage AA but the blend is incompatible (given gpu // limitations) should we disable AA or draw wrong? -#define DISABLE_COVERAGE_AA_FOR_BLEND 0 +#define DISABLE_COVERAGE_AA_FOR_BLEND 1 static const size_t MAX_TEXTURE_CACHE_COUNT = 256; static const size_t MAX_TEXTURE_CACHE_BYTES = 16 * 1024 * 1024; |