Meeting events overview

​

Usage notes

• Engine, IM, camera device, and mic device events share the MeetingEngine lifecycle; assigning null stops new dispatches.
• Room, member, message, and media events are bound to the current meeting and cleared automatically when you exit the meeting; reassign them for the next meeting.
• MeetingRemoteVideoEvent is passed in with a single remote subscription and stops dispatching after you unsubscribe or exit the meeting.
• Callbacks stay on the actual source thread of SRTC, IM, or the network and are not switched to the Android main thread automatically.
• Local and remote raw-frame callbacks run on high-frequency media threads; don’t perform blocking operations in them.
• Each event group provides a corresponding MeetingXxxSimpleEvent empty implementation, so you only override the methods you actually care about.

​

Registration example

engine.engineEvent = object : MeetingEngineSimpleEvent() {
    override fun onError(errorCode: Int, message: String?) {
        // Log global runtime errors
    }
}

engine.userEvent = object : MeetingUserSimpleEvent() {
    override fun onUserEnter(uid: String) {
        // Refresh the member list
    }
}

​

Choosing an event interface