You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From migrating a DefaultControlDispatcher to ForwardingPlayer, do I need to implement something else besides only creating an instance of the ForwardingPlayer class? Because I'm not getting called the method setPlayWhenReady from the ForwardingPlayer but other methods are called as getPlayWhenReady and isPlaying, for example.
This is reproducible in the ExoPlayer Demo app v2.17.1 by just passing a ForwardingPlayer object to the playerView object through the method setPlayer()
Thank you!
The text was updated successfully, but these errors were encountered:
The PlayerControlView is using player.play() and player.pause() which is delegated by the ForwardingPlayer to the wrapped Player. Then the wrapped player is calling setPlayWhenReady(true|false) but not on the ForwardingPlayer but internally on itself.
So you can intercept these calls by overriding play() and pause() of your ForwardingPlayer.
From migrating a
DefaultControlDispatcher
toForwardingPlayer
, do I need to implement something else besides only creating an instance of theForwardingPlayer
class? Because I'm not getting called the methodsetPlayWhenReady
from theForwardingPlayer
but other methods are called asgetPlayWhenReady
andisPlaying
, for example.This is reproducible in the ExoPlayer Demo app v2.17.1 by just passing a
ForwardingPlayer
object to theplayerView
object through the methodsetPlayer()
Thank you!
The text was updated successfully, but these errors were encountered: