Skip to main content

​
Overview

After the player has loaded, it can be controlled programmatically and its state can be queried. The return value of the new BeyondWords.Player(...) call is a player instance: 
const player = new BeyondWords.Player(...);
This instance can be used to get the current time, change the track, set the backgroundColor, etc: 
console.log(player.currentTime);

player.contentIndex = 3;

player.backgroundColor = "red";
The player is reactive and will immediately update with these changes.

​
How to get instances

If you have already initialized the player, e.g. via a script tag, you can get all of the player instances with: 
BeyondWords.Player.instances() // Returns an array.
For example, if you only have one player on your page, you could set its backgroundColor with: 
BeyondWords.Player.instances()[0].backgroundColor = "red";
For convenience the BeyondWords constant is added to the global window object.

​
How overrides work

There are three different places settings can come from:
  1. From the BeyondWords API after setting project and content identifiers
  2. From the initialization code, e.g. in the script tag’s ‘onload’ attribute
  3. From Player SDK calls made by you after the player has loaded
The override order is shown above. Firstly, the player will use properties from the API which can be overridden by the initialization code. Secondly, the player’s properties can be overridden by SDK calls, e.g. to change its backgroundColor. If the player’s identifiers change and a new API request is made, any temporary changes made by SDK calls will be reset. Only changes that were included in the initializer of the player will be persisted when a new API request is made.

​
Player settings

Please refer to the Player Settings for a full list of available settings that can be configured in the player. Additionally, please refer to Player Events if you want to register event listeners for player events.