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

Save app state when closing to tray #968

Closed
tzarebczan opened this issue Jan 26, 2018 · 0 comments
Closed

Save app state when closing to tray #968

tzarebczan opened this issue Jan 26, 2018 · 0 comments
Assignees
Labels
help wanted level: 2 Some knowledge of the existing code is recommended type: improvement Existing (or partially existing) functionality needs to be changed
Milestone

Comments

@tzarebczan
Copy link
Contributor

The Issue

Close to tray app behavior was recently changed by @IGassmann where the app closes and then is re-opened to a fresh state when restoring. Previously, the app state was retained when the app was closed.

If its possible and doesn't cause issues, we should retain app state when closing to tray as other electron apps like Discord do.

Steps to reproduce

  1. Go to a claim
  2. Close LBRY to the app tray (close window)
  3. Restore from tray
  4. Notice app loads to green screen and then to home

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

@tzarebczan tzarebczan added type: improvement Existing (or partially existing) functionality needs to be changed needs: triage labels Jan 26, 2018
@liamcardenas liamcardenas added help wanted level: 2 Some knowledge of the existing code is recommended and removed needs: grooming labels Jan 30, 2018
@lyoshenka lyoshenka added this to the Feb 26 (app) milestone Feb 13, 2018
@lyoshenka lyoshenka modified the milestones: Feb 26 (app), Mar 12 (app) Feb 26, 2018
IGassmann pushed a commit that referenced this issue Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted level: 2 Some knowledge of the existing code is recommended type: improvement Existing (or partially existing) functionality needs to be changed
Projects
None yet
Development

No branches or pull requests

5 participants