Comment on page
The nexxPLAY SDK makes heavy Use of various Events. In order to react to them, the Page must add Listeners to those Event Types, it is interested in.
This is the most used Listeners and receives all Events, that are exposed by a nexxPLAY Player Instance.
The given Function will then be called for every Player related Event of every Player with a lot of Metadata. The Function will get an Object, that can easily be filtered by
object.typeto handle only the Events, the Page is interested in.
Please notice, that this Function will receive ALL Events of ALL Players. If that is not desired, dont use a global Listener, add a Player-specific Listener with the
Here is the current List of all emitted Events (that are related to Media Playback):
Please notice, that on iOS, the Events (Notification) have a different Name, that is built by the following Rule: "nexxPlay" + EventName.camelCase() + "Notification". So for example, a "pause" Notification will become a "nexxPlayPauseNotification", and a "changeplaypos" Notification will become a "nexxPlayChangePlayPosNotification"
Every Event consists of a Data Object besides the Event Name. Accessing the Details varies between Player Technologies, but in General, the Events provide at least basic Information of the Media, that it refers to (EVENT.mediaID, EVENT.globalID, EVENT.streamtype).
These Events are also supported by nexxPLAY for iOS and nexxPLAY for android.
Although the PlaystateListener is the most used Listener, the nexxPLAY SDK offers a variety of other Listener Functionalities, that can be used in advanced Contexts.
//get notified for Addon Events
//get notified for Widget Events
//get notified for LifeCycle Events like "freeze"
//get notified for Network Events like "online, offline"
//get notified for Geo (and Geo Permission) Events