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.

Sign up for GitHub

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

Jump to bottom

Cannot choose another server if the app is already connected to one server #26

Closed
fttx opened this issue May 4, 2017 · 1 comment
Closed

Cannot choose another server if the app is already connected to one server #26

fttx opened this issue May 4, 2017 · 1 comment
Assignees
@fttx
Labels
bug
Milestone
v2.0.0

Comments

@fttx
Copy link
Owner

fttx commented May 4, 2017

Solution: close and open the connection again when a new server is selected
@fttx fttx added the bug label May 4, 2017
@fttx fttx added this to the v1.1.0 milestone May 4, 2017
@fttx fttx self-assigned this May 4, 2017
fttx added a commit that referenced this issue May 4, 2017
@fttx
Disconnect before connecting to another server #26
fdce741
@fttx
Copy link
Owner Author

fttx commented May 4, 2017 •
edited
Loading

The problem seems to be fixed
TODO:

  • force sync existing scannings on the server
  • test it for each platform
  • remove console.log

@fttx fttx modified the milestones: v1.2.0, v1.1.0 May 19, 2017
@fttx fttx removed their assignment Jul 19, 2017
@fttx fttx self-assigned this Aug 18, 2017
fttx added a commit that referenced this issue Aug 18, 2017
@fttx
Trigger reconnect only if the selected server has changed
920f2af 
#26 Fixed
@fttx fttx closed this as completed Aug 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fttx fttx

Labels
bug
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
1 participant
@fttx