XnView 1.91.4 doesn't use it's own INI when loaded on a Toshiba U3 drive, it uses the local version!
BTW: I manually updated the 1.90.3 U3 version
AMD Ryzen 3 3300X 3.8Ghz, 16Gb DDR4, RX6600XT with Dell U2520D at 2560x1440@60Hz scaling 125%
Win11 x64 24H2, Hard Disk Sentinel Pro, MS PowerToys, Process Lasso Pro and Wintoys
XnView always checks the registry first, if that's enabled it'll ignore any ini completely. I haven't tested user ini vs local, maybe that takes precedence as well.
foxyshadis wrote:XnView always checks the registry first, if that's enabled it'll ignore any ini completely. I haven't tested user ini vs local, maybe that takes precedence as well.
Oh right, so you must not have a XnView that use registry to use U3 version...
XnView should use it's own INI stored on the USB drive itself not the same one as on the HDD.
If XnView could be hardcoded like this...
XnView.exe -ini xnview_u3.ini
AMD Ryzen 3 3300X 3.8Ghz, 16Gb DDR4, RX6600XT with Dell U2520D at 2560x1440@60Hz scaling 125%
Win11 x64 24H2, Hard Disk Sentinel Pro, MS PowerToys, Process Lasso Pro and Wintoys
ckit wrote:XnView should use it's own INI stored on the USB drive itself not the same one as on the HDD.
If XnView could be hardcoded like this...
XnView.exe -ini xnview_u3.ini
Ok, the problem is that xnview search settings first in registry, and after in 'Document settings', and after in xnview folder. Perhaps i must search in xnview folder at first step?
xnview wrote:Ok, the problem is that xnview search settings first in registry, and after in 'Document settings', and after in xnview folder. Perhaps i must search in xnview folder at first step?
Yes, it would be useful also when testing a bug with default settings, now it's too complicated.
• Yes, like this.
- It should be convenient for USB devices, and also securer when updating the programme “by hand”
(I'd a hitch once recently, probably because that order of searching…)
KR
Claude
Clo
Old user ON SELECTIVE STRIKE till further notice •
The default behavior in any program should be to check for/react to an ini file in it's own folder before doing anything else. Checking user/windows folders or the registry should always be secondary.