diff options
| author |  brianosman <brianosman@google.com> | 2016-09-23 08:11:55 -0700 |
|---|---|---|
| committer |  Commit bot <commit-bot@chromium.org> | 2016-09-23 08:11:55 -0700 |
| commit | 53c38087949252d27cde668368a3eeb59cc2eb00 (patch) | |
| tree | 9d005cd6e6037f4b64d1140786e4e687f062f063 /gn/gn_to_cmake.py | |
| parent | 27a3aa5921b2aaf95314f955285c3cba91e4c19a (diff) | |
Change SkSpecialImage::makeSurface and makeTightSurface to take output
properties (color space), bounds, and (optional) alphaType.
We were being pretty inconsistent before. Raster was honoring all
components of the info. GPU was using the supplied color type, but
propagating the source's color space. All call sites were saying N32.
What we want to do is propagate the original device's color space, and
pick a good format from that. Rather than force all the clients to
jump through hoops constructing an SkImageInfo that meets our criteria,
just have them supply the few bits we care about, and do everything else
internally.
This also lets us always use RGBA on GPU, but N32 on raster.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2349373004
Review-Url: https://codereview.chromium.org/2349373004
Diffstat (limited to 'gn/gn_to_cmake.py')
0 files changed, 0 insertions, 0 deletions