You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
I am working on the GUI for my networked application and when the client tries to connect I get the NetConnectionStatus.InitiatedConnect in the StatusChange-Message.
When the client is not able to connect immediately it will try 5 more handshake attempts and I want to show the user of my app that it is doing this.
After the StatusChange I only get 5 ErrorMessages, that it failed to send a packet.
I want to show the user: Trying to connect...
And then something like "Trying to connect(1)", "Trying to connect(2)", "Trying to connect(3)"...
But I can't seem to access any information that the client is resending the handshake attempt/trying to connect again.
I think a StatusChange-Message would be nice or some other kind of event.
Any ideas on how to achieve this behaviour? Do I have to extend lidgren network for this or can this be achieved with the current version?
The text was updated successfully, but these errors were encountered:
Hello.
I am working on the GUI for my networked application and when the client tries to connect I get the NetConnectionStatus.InitiatedConnect in the StatusChange-Message.
When the client is not able to connect immediately it will try 5 more handshake attempts and I want to show the user of my app that it is doing this.
After the StatusChange I only get 5 ErrorMessages, that it failed to send a packet.
I want to show the user: Trying to connect...
And then something like "Trying to connect(1)", "Trying to connect(2)", "Trying to connect(3)"...
But I can't seem to access any information that the client is resending the handshake attempt/trying to connect again.
I think a StatusChange-Message would be nice or some other kind of event.
Any ideas on how to achieve this behaviour? Do I have to extend lidgren network for this or can this be achieved with the current version?
The text was updated successfully, but these errors were encountered: