Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

Netshroud
Copy link

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.

@codecov-io
Copy link

Current coverage is 17.57%

Merging #205 into master will decrease coverage by -0.01% as of cddcf30

@@            master    #205   diff @@
======================================
  Files           67      67       
  Stmts         7292    7294     +2
  Branches       520     520       
  Methods          0       0       
======================================
  Hit           1282    1282       
  Partial         73      73       
- Missed        5937    5939     +2

Review entire Coverage Diff as of cddcf30

Powered by Codecov. Updated on successful CI builds.

@Netshroud Netshroud added this to the 1.7.0 milestone Dec 13, 2015
@Netshroud Netshroud changed the title First attempt at resolving #181 Mark LogOff-triggered disconnections as user-initiated Dec 13, 2015
@Netshroud
Copy link
Author

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; }
Copy link
Member

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.

Copy link
Author

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.

Copy link
Member

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.

Netshroud pushed a commit that referenced this pull request Dec 20, 2015
@Netshroud Netshroud closed this Dec 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants