aboutsummaryrefslogtreecommitdiffhomepage
path: root/include
diff options
context:
space:
mode:
authorGravatar brianosman <brianosman@google.com>2016-12-01 09:02:03 -0800
committerGravatar Commit bot <commit-bot@chromium.org>2016-12-01 09:02:03 -0800
commit9db12d2341f3f8722c8b90b11dd4cce138a8a64e (patch)
tree946c356960dcd2ec444a32ce0ee8570407d81dcf /include
parent9afd371a8a66f992f98eb2a3fc75ae64bddc730b (diff)
Two (related) changes here:
1) Our older iOS devices failed our sRGB tests, due to precision issues with alpha. At this point, we only test on iPadMini 4, and that appears not to have any problems. 2) iOS devices still don't have the sRGB texture decode extension. But, some clients have no interest in mixing legacy/color-correct rendering, and would like to use sRGB on these devices. This GrContextOptions flag enables sRGB support in those cases. Adjust the test code to produce sRGB capable contexts on these devices, but only for configs that have a color space. (See comment). BUG=skia:4148 Review-Url: https://codereview.chromium.org/2539993002
Diffstat (limited to 'include')
-rw-r--r--include/gpu/GrContextOptions.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/include/gpu/GrContextOptions.h b/include/gpu/GrContextOptions.h
index 6a1b51b5a6..65daf72ead 100644
--- a/include/gpu/GrContextOptions.h
+++ b/include/gpu/GrContextOptions.h
@@ -77,6 +77,14 @@ struct GrContextOptions {
* purposes.
*/
bool fForceSWPathMasks = false;
+
+ /**
+ * If true, sRGB support will not be enabled unless sRGB decoding can be disabled (via an
+ * extension). If mixed use of "legacy" mode and sRGB/color-correct mode is not required, this
+ * can be set to false, which will significantly expand the number of devices that qualify for
+ * sRGB support.
+ */
+ bool fRequireDecodeDisableForSRGB = true;
};
#endif