aboutsummaryrefslogtreecommitdiffhomepage
path: root/dm/DMSrcSinkAndroid.h
diff options
context:
space:
mode:
authorGravatar brianosman <brianosman@google.com>2016-09-23 13:04:05 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-09-23 13:04:05 -0700
commiteed6b0e1d865a1f93143c09961debba0aca592ca (patch)
tree961a464d586a0f11007b8a9a482df912e8c5d305 /dm/DMSrcSinkAndroid.h
parent49da334086c4a2c0bc4cb99e97965600dcb72f73 (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 Committed: https://skia.googlesource.com/skia/+/53c38087949252d27cde668368a3eeb59cc2eb00 Review-Url: https://codereview.chromium.org/2349373004
Diffstat (limited to 'dm/DMSrcSinkAndroid.h')
0 files changed, 0 insertions, 0 deletions