aboutsummaryrefslogtreecommitdiffhomepage
path: root/samplecode
diff options
context:
space:
mode:
authorGravatar Brian Osman <brianosman@google.com>2016-11-01 15:56:16 -0400
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2016-11-01 20:55:51 +0000
commit7039f74a8b1d39b9c44fd357912ce66e6bc9fd25 (patch)
tree8fdd34da5bb77fd883f762932ba7d227c0cdf64f /samplecode
parentafac581523af9de5e0af0af1dc128cac1b846006 (diff)
Remove SkImageInfoIsGammaCorrect, etc...
Our internal definition is (and will continue to be) that anything with a color space is gamma correct. F16 is irrelevant (whether or not we choose to support untagged F16). This makes these helpers less than helpful, and lets us remove them from (public) API. API change is just removal (of unused functions). TBR=reed@google.com BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=4228 Change-Id: Ia84a423548bfee14a3ba4a43d6d5b8c4686fb5ff Reviewed-on: https://skia-review.googlesource.com/4228 Commit-Queue: Brian Osman <brianosman@google.com> Reviewed-by: Mike Klein <mtklein@chromium.org>
Diffstat (limited to 'samplecode')
-rw-r--r--samplecode/SampleApp.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/samplecode/SampleApp.cpp b/samplecode/SampleApp.cpp
index 6f0e95842e..6722429618 100644
--- a/samplecode/SampleApp.cpp
+++ b/samplecode/SampleApp.cpp
@@ -350,7 +350,7 @@ public:
// With ten-bit output, we need to manually apply the gamma of the output device
// (unless we're in non-gamma correct mode, in which case our data is already
// fake-sRGB, like we're expected to put in the 10-bit buffer):
- bool doGamma = (fActualColorBits == 30) && SkImageInfoIsGammaCorrect(win->info());
+ bool doGamma = (fActualColorBits == 30) && win->info().colorSpace();
SkPaint gammaPaint;
gammaPaint.setBlendMode(SkBlendMode::kSrc);