-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark LogOff-triggered disconnections as user-initiated #205
Conversation
Current coverage is
|
1f740e3
to
348600c
Compare
Re-did this a lot simpler to resolve #181. |
/// If this is true when the connection is closed, the <see cref="SteamClient.DisconnectedCallback"/>'s <see cref="SteamClient.DisconnectedCallback.UserInitiated"/> property | ||
/// will be set to <c>true</c>. | ||
/// </summary> | ||
public bool ExpectDisconnection { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think this needs to be entirely public, consumers might be able to misuse it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking that, but I don't want our own ClientMsgHandlers
to be able to do things that consumer-built ones cannot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CMClient could likely handle that logic based on the emsg being passed to Send
.
Had to do a few hacky things I don't particularly like. Any suggestions to improve this?
Ideally, this probably needs a full-blown state machine.