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
Currently it is possible to define different UI variants that are switched according to criteria provided by the UIConditionContext object when certain player events happen. This means it is only possible to set the criteria for certain UI variants at setup, but switching is done autonomously and internally in the UIManager without any means to interfere from outside. Desired is an API that also allows to trigger switching from outside at any desired time.
The UIConditionContext upon which the target UI variant is evaluated:
Since the UI variants do not have distinct IDs, it is not possible to directly switch to a specific variant, e.g. uimanager.switchToVariant(UIVariant.Ads). The API will thus somehow have to work with the UIConditionContext and allow setting the conditions so the switching code evaluates to the desired UI variant.
Currently it is possible to define different UI variants that are switched according to criteria provided by the
UIConditionContext
object when certain player events happen. This means it is only possible to set the criteria for certain UI variants at setup, but switching is done autonomously and internally in theUIManager
without any means to interfere from outside. Desired is an API that also allows to trigger switching from outside at any desired time.The
UIConditionContext
upon which the target UI variant is evaluated:bitmovin-player-ui/src/ts/uimanager.ts
Lines 80 to 118 in d8a6978
Example UI variants and criteria setup:
bitmovin-player-ui/src/ts/uimanager.ts
Lines 654 to 672 in d8a6978
The events that trigger the evaluation of the context and potentially switch the UI variant:
bitmovin-player-ui/src/ts/uimanager.ts
Lines 339 to 349 in d8a6978
The text was updated successfully, but these errors were encountered: