aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/user/sample/color.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/user/sample/color.md')
-rw-r--r--site/user/sample/color.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/site/user/sample/color.md b/site/user/sample/color.md
index 3f4d869504..28d86d396d 100644
--- a/site/user/sample/color.md
+++ b/site/user/sample/color.md
@@ -116,9 +116,11 @@ can be in any gamut, but must have a linear transfer function.
sk_sp<SkImage> MakeFromEncoded(sk_sp<SkData> encoded);
// Create an image from a texture in a particular color space
- sk_sp<SkImage> MakeFromTexture(GrContext*, const GrBackendTexture&,
- GrSurfaceOrigin, SkAlphaType, sk_sp<SkColorSpace>,
- ...);
+ // Caution: There are versions of this constructor that do not take an
+ // SkColorSpace. But without an SkColorSpace, Skia does not have
+ // enough information to draw correctly.
+ sk_sp<SkImage> MakeFromTexture(GrContext*, const GrBackendTextureDesc&,
+ SkAlphaType, sk_sp<SkColorSpace>, ...);
**SkBitmap** is another (not preferred) representation for image sources. Be careful to not forget
the color space.
@@ -188,5 +190,4 @@ cannot know how to draw without knowing the color space of the source.
It is possible to create **an object that is both a source and destination**, if Skia will both
draw into it and then draw it somewhere else. The same rules from above still apply, but it is
subtle that the color space tag could have an effect (or no effect) depending on how the object is
-used.
-
+used. \ No newline at end of file