Where Does qView Store Settings?
Where qView keeps options and recents on Windows, Mac and Linux, and why Windows uses the registry instead.
Last updated
qView stores options through Qt settings, which land in the native store for each OS. Windows builds write registry keys under the app branch. Linux builds write an ini file in the config home. Mac builds write a preferences plist.
That split surprises anyone moving settings across systems with one script. Portable file mode was requested upstream but never shipped, so the exe folder stays inert. Back up the native store per OS rather than hunting one universal file. Slideshow timers and window geometry share the same store, so one export covers all.
Where qView stores this, by platform
HKEY_CURRENT_USER\Software\qView\qView
Registry branch with options and recents keys. No portable file mode exists despite requests. Export the branch to roam settings.
~/.config/qView/qView.conf
Qt native ini mapping for the same options. Shares option names with the Windows keys. Copy the file between Linux machines.
~/Library/Preferences/com.qView.qView.plist
Qt native plist mapping for the same options. Read it with defaults or a plist editor. Copy between Macs with the app closed.
Frequently asked questions
Why does qView use the registry instead of a file?
Because Qt maps settings to the native store per OS, which means registry keys on Windows. Linux gets an ini file and Mac gets a plist for the same options. Export the registry branch to roam Windows settings between machines.
Can I make qView portable with a config next to the exe?
No. Portable file mode was requested but never implemented, so the exe directory stays ignored on Windows. Installed builds always write the registry branch in this post. Use the registry export for machine moves.
Notice an outdated path? Let us know.