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

"hidden" config in windows needs to be standardized #319

Open
ppbrown opened this issue Jan 3, 2025 · 5 comments
Open

"hidden" config in windows needs to be standardized #319

ppbrown opened this issue Jan 3, 2025 · 5 comments

Comments

@ppbrown
Copy link

ppbrown commented Jan 3, 2025

I just downloaded, install, and ran the release for windows.

I mistakenly pointed it at a directory with many subdirectories and files. So it effectively hangs.

i killed it, tried to start it up.... but it hangs still. I think it preserved myu old request and is trying to reopen.

I want to just remove the config file and start fresh. but it doesnt seem to be using the linux standard location, OR the windows standard.

linux standard would be $HOME/.config/taggui or whatever.

not there.

windows standard would be %APPDATA%\local\taggui or worst case, %appdata%\roaming\taggui

but I dont see it there either.

????

@jhc13
Copy link
Owner

jhc13 commented Jan 3, 2025

See #53 or #90.

@ppbrown
Copy link
Author

ppbrown commented Jan 3, 2025

okay, thanks for the info, but.. it doesnt change the underlying issue of this issue.

The config is non-standard. even for windows, pretty much nobody uses "The registry" any more.
Why not just delete the windows specific code and let both sides use the $HOME/.config/taggui directory in exactly the same way?

@jhc13
Copy link
Owner

jhc13 commented Jan 3, 2025

Why not just delete the windows specific code and let both sides use the $HOME/.config/taggui directory in exactly the same way?

There is no Windows-specific code. It's the default location for PySide6.

@jhc13
Copy link
Owner

jhc13 commented Jan 3, 2025

I agree that the current setup has some problems and should be improved.

@pbrownrobo
Copy link

scanning through that doc, seems like all you need to do is change QSettings.Format from NativeFormat to QSettings.IniFormat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants