-
-
Notifications
You must be signed in to change notification settings - Fork 63
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
PicView always starts at this postition on my win10 pc - why?! The bottom part is always out of the view 馃 #149
Comments
I've tried to replicate your issue, though I'm unable to reproduce it. Is it possible you can provide me further details? |
How can I help you further here? What infos do you need? |
If you click the space bar button, will it center the window? Have you tried resetting the settings for PicView? You can reapply them afterwards. I'll have a new option in the settings window in the next release to reset settings to default. |
Sorry about the inconvenience. The issue is cause of Windows not giving writing permissions to save settings. To solve the issue, you can run PicView as admin (when you need to save settings) or reinstall it to a new location, with writing permission (usually somewhere else than E.G, C:\Program Files) Additionally, I've uploaded a new version to fix the saving issue. I would appreciate it if you would download a new version here https://sourceforge.net/projects/picview/files/%23149%2C%23137/, extract it and replace the files where PicView is located on your machine and tell me if it fixes your issue, instead of running it as admin or reinstalling it. |
The new version stores my changed settings 馃憤 When I see it correct you now save UserSettings.json file in roaming directory in such cases? |
Thank you for confirming. Yes, it's supposed to save and read from there in case of lack of writing permissions. |
The changes has been added in the 2.2.5 version. |
And yes, it's still the same with newest v2.2.4
Originally posted by @Heart1010 in #143 (comment)
The text was updated successfully, but these errors were encountered: