Process join responses and events
Understand what events your game should to listen to during the joining process.
읽는 시간 2분최근 업데이트: 8달 전
When joining a channel there are two types of events your game should be configured to listen to. The first set of events will give you the status of the audio and text channels. The second set of events will provide information for UI events to manage a roster of “in-channel” users.
Audio and text event responses
Audio events:
void HandleMediaStreamUpdatedEvent(vx_evt_media_stream_updated *evt){ if (evt->state == session_media_connected) { printf("Audio Connected to %s\n", evt->session_handle);
Text events:
void HandleTextStreamUpdatedEvent(vx_evt_text_stream_updated *evt){ if (evt->state == session_text_connected) { printf("Text Connected to %s\n", evt->session_handle);
Use media to respond to audio events and use text to respond to text channel events. Craft responses to both if both text and audio are being used.
Participant updated events
Participant updated events allow you to manage a list of in-channel users for use in your game UI or elsewhere in your application.
void HandleParticipantAddedEvent(vx_evt_participant_added *evt){ //use this to update your roster/game that a player has joined a channel}void HandleParticipantRemovedEvent(vx_evt_participant_removed *evt){ //use this to update your roster/game that player has left a channel}void HandleParticipantUpdatedEvent(vx_evt_participant_updated *evt){ //this indicates when a player is speaking, not speaking, and other key player events}
When tracking participant state, it is important to use the field as the unique identifier of the participant. This allows the game to distinguish between users who have left a channel and users who have rejoined a channel.
encoded_uri_with_tag참고
Use the field to distinguish between events that pertain to the local user from events that pertain to other users.
is_current_userNext step, check for errors and verify your implementation.