-
Notifications
You must be signed in to change notification settings - Fork 69
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
v2.0.45 Settings backup not writing a settings.txt file #424
Comments
Did you use the Backup button or the Save button? With Backup, I get a settings.txt file in the directory. Another possibility, does the directory require Administrator privilege? |
Definitely clicking backup. Admin privileges for the folder could well be it. Will double check. |
I've never quite understood how the whole admin thing works in Windows when you try to write to something that you don't have privilege to. I think a lot of apps fail silently. Is there a failure notification that happens at the application level? If it does, it would be really nice for ioSender to notify the user - could make it easy to solve related problems. |
It is a bit strange because I don't recall changing the program folder permissions for the previous release, and it's in the same place. |
I'm also having issues with my settings. If I add a new probe profile, set my settings and close ioSender my profile is gone. Is there a was to same probing profiles in version 2.45? I also tried 2.44 and have the same issue. |
I am not able to replicate this.
Agree, I'll add that - currently I have empty catch blocks so saving will fail silently. |
This is likey related to UAC, i'mm pretty sure i still have enabled on my computer and I have moved the application to the Program Files folder. I will report back. |
New edge version uploaded. |
Not sure if it's an issue specific to my machine, but the previous release saved the settings backup with no issue. Latest release gives the usual message that a settings.txt file was saved, but it's not in the folder.
The text was updated successfully, but these errors were encountered: