From 4ea4f632da86c8462cfc49039a54836afbcae57f Mon Sep 17 00:00:00 2001 From: Sumir Kataria Date: Tue, 29 Mar 2022 15:44:37 +0000 Subject: [PATCH] Add documentation clarifying the differences between Surface/TextureView Test: Built docs Change-Id: Iec47b85bbfc537932832b1ad3fa98975a93075df --- core/java/android/view/TextureView.java | 41 +++++++++++++++++++++++-- 1 file changed, 39 insertions(+), 2 deletions(-) diff --git a/core/java/android/view/TextureView.java b/core/java/android/view/TextureView.java index b55ae1e7e468d..15e0cce9af10e 100644 --- a/core/java/android/view/TextureView.java +++ b/core/java/android/view/TextureView.java @@ -41,6 +41,43 @@ import android.util.Log; *

TextureView can only be used in a hardware accelerated window. When * rendered in software, TextureView will draw nothing.

* + *

TextureView vs. SurfaceView Capabilities

+ + *

+ * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + * + *
 TextureViewSurfaceView
Supports alphaX 
Supports rotationsX 
Supports clippingX 
HDR supportLimited (on Android T+)Full
Renders DRM content X
+ *

+ * *

Unlike {@link SurfaceView}, TextureView does not create a separate * window but behaves as a regular View. This key difference allows a * TextureView to have translucency, arbitrary rotations, and complex @@ -51,8 +88,8 @@ import android.util.Log; * hierarchy is that it may have slower performance than * SurfaceView. TextureView contents must be copied, internally, from the * underlying surface into the view displaying those contents. For - * that reason, SurfaceView is recommended as a more general solution - * to problems requiring rendering to surfaces.

+ * that reason, SurfaceView is recommended as a more general solution + * to problems requiring rendering to surfaces.

* *

Using a TextureView is simple: all you need to do is get its * {@link SurfaceTexture}. The {@link SurfaceTexture} can then be used to