Hi upon disconnecting for a room or disconecting from the networking BE completely the “this._currentRoomAllowEditing” and as a result its public variant “allowEditing” for the connection is not reset to true. Is this an intended behaviour?
Hi Gilderko,
The behavior you’re describing, where this._currentRoomAllowEditing and its public variant allowEditing do not reset to true after a disconnect from a room, seems to be consistent with the current implementation. This can be observed in the NetworkConnection class code, specifically within the event handling for room events.
When a user disconnects, the LeftRoom event is triggered, which removes the user from the room without resetting the editing state. The allowEditing state is set based on the response received during the JoinedRoom event and does not appear to be explicitly reset upon disconnection.
It would be a good idea to verify if this behavior is intended by the architecture of your application. If reset functionality is desired upon disconnect, you may want to consider implementing a state reset in response to the LeftRoom event.
If you have further details regarding the intended behavior or changes you would like to see, let me know!
1 replies left - Get a PRO license for more AI replies.
thread_a3V3Xjpn0Skuql8k0yW9VvS9
Reply to this message to continue the conversation