diff options
| author |  brianosman <brianosman@google.com> | 2016-04-13 13:10:14 -0700 |
|---|---|---|
| committer |  Commit bot <commit-bot@chromium.org> | 2016-04-13 13:10:14 -0700 |
| commit | b461d3457567cf79a3efac3123c00f7afc37fecb (patch) | |
| tree | 6b1600d0da18cefc3e29568419354bd68c9e5b41 /dm | |
| parent | 54ef1a7c95bcc8e507f7d6ccd9a49bd9a110ba90 (diff) | |
Rename lots of things from 'sRGB' to 'GammaCorrect', where appropriate
Trying to be much more explicit about where we really mean sRGB as a format,
and where we mean gamma-correct, as in: "not legacy behavior". Most of the
changes to rendering behavior are dependent on the latter, so let's be precise.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1884873006
Review URL: https://codereview.chromium.org/1884873006
Diffstat (limited to 'dm')
| -rw-r--r-- | dm/DMGpuSupport.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/dm/DMGpuSupport.h b/dm/DMGpuSupport.h index 173befd070..742ec189a5 100644 --- a/dm/DMGpuSupport.h +++ b/dm/DMGpuSupport.h @@ -37,7 +37,7 @@ static inline sk_sp<SkSurface> NewGpuSurface( bool useDIText) { uint32_t flags = useDIText ? SkSurfaceProps::kUseDeviceIndependentFonts_Flag : 0; if (SkImageInfoIsGammaCorrect(info)) { - flags |= SkSurfaceProps::kAllowSRGBInputs_Flag; + flags |= SkSurfaceProps::kGammaCorrect_Flag; } SkSurfaceProps props(flags, SkSurfaceProps::kLegacyFontHost_InitType); return SkSurface::MakeRenderTarget(grFactory->get(type, options), SkBudgeted::kNo, |