Remove more references to overriding layouts from Player(Control)View

In exoplayer2 this affects StyledPlayer(Control)View

#minor-release

PiperOrigin-RevId: 481878940
This commit is contained in:
ibaker 2022-10-18 10:55:13 +00:00 committed by Rohit Singh
parent 3399f4ecdf
commit cc1d35cfd7
2 changed files with 11 additions and 19 deletions

View File

@ -85,12 +85,13 @@ import java.util.concurrent.CopyOnWriteArrayList;
/**
* A view for controlling {@link Player} instances.
*
* <p>A PlayerControlView can be customized by setting attributes (or calling corresponding
* <p>A {@code PlayerControlView} can be customized by setting attributes (or calling corresponding
* methods), or overriding drawables.
*
* <h2>Attributes</h2>
*
* The following attributes can be set on a PlayerControlView when used in a layout XML file:
* The following attributes can be set on a {@code PlayerControlView} when used in a layout XML
* file:
*
* <ul>
* <li><b>{@code show_timeout}</b> - The time between the last user interaction and the controls
@ -149,22 +150,14 @@ import java.util.concurrent.CopyOnWriteArrayList;
* <li>Corresponding method: {@link #setTimeBarMinUpdateInterval(int)}
* <li>Default: {@link #DEFAULT_TIME_BAR_MIN_UPDATE_INTERVAL_MS}
* </ul>
* <li><b>{@code controller_layout_id}</b> - Specifies the id of the layout to be inflated. See
* below for more details.
* <ul>
* <li>Corresponding method: None
* <li>Default: {@code R.layout.exo_player_control_view}
* </ul>
* <li>All attributes that can be set on {@link DefaultTimeBar} can also be set on a
* PlayerControlView, and will be propagated to the inflated {@link DefaultTimeBar} unless the
* layout is overridden to specify a custom {@code exo_progress} (see below).
* <li>All attributes that can be set on {@link DefaultTimeBar} can also be set on a {@code
* PlayerControlView}, and will be propagated to the inflated {@link DefaultTimeBar}.
* </ul>
*
* <h2>Overriding drawables</h2>
*
* The drawables used by PlayerControlView (with its default layout file) can be overridden by
* drawables with the same names defined in your application. The drawables that can be overridden
* are:
* The drawables used by {@code PlayerControlView} can be overridden by drawables with the same
* names defined in your application. The drawables that can be overridden are:
*
* <ul>
* <li><b>{@code exo_styled_controls_play}</b> - The play icon.

View File

@ -159,15 +159,14 @@ import org.checkerframework.checker.nullness.qual.RequiresNonNull;
* </ul>
* <li>All attributes that can be set on {@link PlayerControlView} and {@link DefaultTimeBar} can
* also be set on a PlayerView, and will be propagated to the inflated {@link
* PlayerControlView} unless the layout is overridden to specify a custom {@code
* exo_controller}.
* PlayerControlView}.
* </ul>
*
* <h2>Overriding drawables</h2>
*
* The drawables used by {@link PlayerControlView} (with its default layout file) can be overridden
* by drawables with the same names defined in your application. See the {@link PlayerControlView}
* documentation for a list of drawables that can be overridden.
* The drawables used by {@link PlayerControlView} can be overridden by drawables with the same
* names defined in your application. See the {@link PlayerControlView} documentation for a list of
* drawables that can be overridden.
*/
public class PlayerView extends FrameLayout implements AdViewProvider {