From 68943be01deccb0f932ab7a51aff5154d363c701 Mon Sep 17 00:00:00 2001 From: Matt Pietal Date: Wed, 17 Jun 2020 15:41:48 -0400 Subject: [PATCH] Controls API - Update template docs Add more clarity around which control template to select. Fixes: 150630500 Test: manual Change-Id: I215e485e1cf81aae7e2c6c8b469945069136aad8 --- core/java/android/service/controls/Control.java | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/core/java/android/service/controls/Control.java b/core/java/android/service/controls/Control.java index 8383072a48e32..2868f1bf35471 100644 --- a/core/java/android/service/controls/Control.java +++ b/core/java/android/service/controls/Control.java @@ -789,6 +789,13 @@ public final class Control implements Parcelable { } /** + * Set the {@link ControlTemplate} to define the primary user interaction + * + * Devices may support a variety of user interactions, and all interactions cannot be + * represented with a single {@link ControlTemplate}. Therefore, the selected template + * should be most closely aligned with what the expected primary device action will be. + * Any secondary interactions can be done via the {@link #setAppIntent(PendingIntent)}. + * * @param controlTemplate instance of {@link ControlTemplate}, that defines how the * {@link Control} will behave and what interactions are * available to the user