SkImage::NewFromYUVTexturesCopy

include/core/SkImage.h

Index: include/core/SkImage.h
diff --git a/include/core/SkImage.h b/include/core/SkImage.h
index 7128f6ea3a2f7cda78ac8a91fe5aedd7df296782..33ae448072cbe81929f5b6342fc607978a0a1f04 100644
--- a/include/core/SkImage.h
+++ b/include/core/SkImage.h
@@ -82,6 +82,16 @@ public:
     static SkImage* NewFromTextureCopy(GrContext*, const GrBackendTextureDesc&,
                                        SkAlphaType = kPremul_SkAlphaType);
 
+    /**
+     *  Create a new image by copying the pixels from the specified y, u, v textures. The data
+     *  from the textures is immediately ingested into the image and the textures can be modified or
+     *  deleted after the function returns. The image will have the dimensions of the y texture.
+     */
+    static SkImage* NewFromYUVTexturesCopy(GrContext*, SkYUVColorSpace,

[Daniele Castagna, 2015/05/27 05:28:56]

Can we also have NewFromYUVTexture that behaves similarly to NewFromTexture
(safe to delete textures after draw/flush when not drawing to a SkPicture)?

In that way we could avoid a copy in SkCanvasVideoRenderer::Paint.

+                                           const GrBackendObject yuvTextureHandles[3],
+                                           const SkISize yuvSizes[3],
+                                           GrSurfaceOrigin);
+
     int width() const { return fWidth; }
     int height() const { return fHeight; }
     uint32_t uniqueID() const { return fUniqueID; }