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

Add "autoconnect" option #154

Closed
tkem opened this issue Dec 13, 2015 · 2 comments
Closed

Add "autoconnect" option #154

tkem opened this issue Dec 13, 2015 · 2 comments

Comments

@tkem
Copy link
Owner

tkem commented Dec 13, 2015

  • Store WS-URL (and name?) of last server in user settings.
  • At startup, automatically connect to last server.
  • If connection fails, show current server selection.
  • If connection succeeds, show notification (toast?), e.g. "Connected to...".
  • Make this configurable in "Look and feel" settings, since devs may prefer current behavior.
@tkem
Copy link
Owner Author

tkem commented Jan 8, 2016

Additionally investigate startup time; though splash screen should be hidden when first server is detected, this still seems to take too long.

@tkem tkem added this to the v1.7.0 milestone Jan 9, 2016
@tkem tkem modified the milestones: v1.7.0, v1.8.0 Apr 13, 2016
@tkem tkem modified the milestone: v1.8.0 May 1, 2016
tkem added a commit that referenced this issue Mar 17, 2017
@tkem
Copy link
Owner Author

tkem commented Mar 18, 2017

This has become more relevant with introduction of the MusicControls plugin, especially when the app is killed by the system and a click on the notification icon/cover restarts the app.
So it would be preferable to always try to connect to the last server at startup, with a (configurable?) timeout.

@tkem tkem closed this as completed in 7fc5c4f Mar 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant