Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

"Launch Toastify with Windows" setting is not saved #55

Closed
Kilay opened this issue Mar 19, 2018 · 7 comments
Closed

"Launch Toastify with Windows" setting is not saved #55

Kilay opened this issue Mar 19, 2018 · 7 comments

Comments

@Kilay
Copy link

Kilay commented Mar 19, 2018

When I check "Launch Toastify with Windows" setting and saved, notification says that "Settings Saved" but if I close Toastify and start it again, the setting is not checked anymore. And Toastify does not start when I start Windows.

Also, when I check the "Launch Toastify with Windows" setting, I can see the process added in my Task Manager (under startup tab). If I close Toastify, the process stay in startup tab but as soon as I start Toastify again, it disappear from startupt tab

EXPECTED BEHAVIOUR

Toastify should be launched with Windows

ACTUAL BEHAVIOUR

Toastify is not launched

STEPS TO REPRODUCE THE BEHAVIOUR

Check "Launch Toastify with Windows" in settings
Save settings
Reboot Windows

LOG FILE

Toastify.log
Toastify.cfg.txt

@aleab
Copy link
Owner

aleab commented Mar 19, 2018

Hi @Kilay!
Your issue has already been reported in #52. It'll be fixed in the next release.

@aleab
Copy link
Owner

aleab commented Mar 19, 2018

I'll actually leave this issue open, so it's easier to see it in case anyone comes around with the same problem. 😄

@aleab aleab reopened this Mar 19, 2018
@Kilay
Copy link
Author

Kilay commented Mar 19, 2018

Once again, thanks for the quick response and the hard work :D
Will wait the next release.

@Clarky3
Copy link

Clarky3 commented Mar 24, 2018

Any update on the next release?

@aleab
Copy link
Owner

aleab commented Mar 24, 2018

@clarkycal I'm currently working on #46 (for which I'm waiting for this pull request to be approved and implemented in an official version of SpotifyAPI-NET), #47 and #49.
I wanted to bundle them all up in the next release; at the very minimum, if I can't fix #47 and #49 quickly, I want to include the fix for #46 which seems to be the greatest issue at the moment.

@Clarky3
Copy link

Clarky3 commented Mar 24, 2018

@aleab Very well, sound good! Can't wait.

@aleab
Copy link
Owner

aleab commented Mar 31, 2018

Fixed in new version v1.10.7!

@aleab aleab closed this as completed Mar 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants