simon wrote:Oups, sorry, I did not notice that there was an email box included in the forum, i just checked my usual mail box. I have replaced v220 by 221, and did not change anything else. Results are rather strange.
1) about tags, it works normally (tags are memorized, and if I delete the category.db file, a new one is generated in the same folder (C:\Program Files (x86)\XnView\cache), but sometimes with a few second delay
So the problem with .ini/.db is gone?
2) however, most often, after starting xnview directly, it takes about 5 s to open the browser; Sometimes attempting to open the brower result in a crash, and sometimes the brower opens almost instantly
3) starting xnview by clicking on an associated (e.g. .jpg or .png) file takes about 17 (seventeen !!) seconds, but finally it opens the file normally
Some additional information about 213 vs 220 vs 221. Today, I have attempted to have v220 working on my tower. This was a bloody fight. I finaly realized that (1) v213 and v220 do not use the folders in the same way and (2) there remains a "CustomIniPathFolder=C:\Program Files (x86)\XnView" in the ini file that makes v220 not to work correctly (independently of the fact that the ini file could be or not in this folder) whereas v213 is able to use it, or to look into other folders (roaming, virtual store) if the ini file is not found there. When starting from a completely new ini file, v220 works correctly. Afterwards, using copy and paste from the old ini, i was able to customize xnview as before and still have v220 working normally, and replacing v220 by v221 lead to no perceptible changes (in contrast v220 works normally on my laptop with the ini file together with the exe file, and with this confiiguration, v221 behaves strangely). Also no problem to have v220 to run on windows 8. Finally my initial error was just to attempt to use my previous ini file to keep my customization, although this methods works fine up to v213.
I did not test 221 intensively, but apparently v221 behaves as v220, and both behave as v213 (i.e. work fine) provided the .ini file is not in the program files\xnview folder, and does not mention that CustomIniPathFolder corresponds to this folder. Also V220 seems to be more flexible than v221 in accepting .ini in program files\xnview folder. From this point of view, v213 is the best in being able to work with any folder configuration
simon wrote:Also V220 seems to be more flexible than v221 in accepting .ini in program files\xnview folder. From this point of view, v213 is the best in being able to work with any folder configuration
I did some additional testing on my tower. Indeed, v221 seems to work as 213 here: if there is an "old" .ini with the .exe, v221 as v213 is able to read it but will create a new ini somewhere else (in virtual store or roaming), and tagging works normally. It seems also that .db cannot be stored with the .exe (in a cache subdirectory) using v221 even if I asked for in the option settings. Strangely on my laptop, v221 does not work in this way. I was able to have the .db files stored with .exe using v220, and replacing it by v221 has resulted in a strange behaviour. Since I have started using windows 7, i have noticed that xnview (v213 and older ones) does not work exactly the same way on different computers (in all cases, I attempted to have the .ini and .exe files together, as I didn't know that this may be an issue, and this works on some computers but not on some others). I will attempt to have v221 working normally on my laptop (by moving .db storing elsewhere) and let you know ...
yes, but not on every computer, and not at the first attempt. There should be a kind a backdoor in windows 7 that I used without really knowing how. But given the problems it generated, in the future I will avoid to use c:\program files to store any configuration file for any software
Back to my laptop today, where both v213 and 220, but not v221, work fine with .ini in the .exe folder (and .db as well, but in a subdirectory). I have changed all that to have .ini and .db files in the roaming\xnview directory (by selecting "user" in the option settings). Both v213 and 220 still work fine, but v221 continues to behave strangely (it works, including tagging, but results in delays (although shorter than previously) and makes the windows blinking at launching. I have no idea why (1) I was able to have v213 or 220 xnview working with the .ini file in the .exe folder on this computer but not the other one, and (2) why in standard configuration, v221 works as 220 and 213 on the other computer but not on this one. Both computers are running under windows 7 pro 64 bits. Probably I did not exactly the same things in installing xnview on each one, but I can't guess what.
Inially I had a small delay both at launching and for tagging with v220. Afterwards, I found a configuration with all files (ini, db, exe) in the same directory (program files (x86)\xnview) and no more problems (v220 working as fine as v213). With this configuration I had a huge delay (17s) in lauching v221 (but not in tagging). With the new configuration I set this morning (ini and db in user folder), v213 and v220 still work fine (no delay in launching, tagging or anything else), but v221 shows a delay in lauching (but not in tagging), about 1-2 s rather than 17s where nothing happens, Then xnview opens; Attempting to launch the brower takes 1-2 s additional delay and results in blinking: xnview disappears behind the previously active windows and reappears just after ... or not: sometimes it does not reappears but it is still open (no crash), just hidden behind the other window. Using my previous ini or letting v221 creates a completely new one from scracth does not change anything. Very strange indeed.
No, the two .db were very small. And the same ini was used for v213 to v221 (although I used different ini in time, from a old one to a fully new one). But, as I told you, it is hard to draw general conclusions as finally i was able to have the 3 versions working fine on a computer, but only v213 and v220 working fine on my laptop, with (apparently) the same configuration on both computers (same OS and folder organisation).
simon wrote:No, the two .db were very small. And the same ini was used for v213 to v221 (although I used different ini in time, from a old one to a fully new one). But, as I told you, it is hard to draw general conclusions as finally i was able to have the 3 versions working fine on a computer, but only v213 and v220 working fine on my laptop, with (apparently) the same configuration on both computers (same OS and folder organisation).
Really strane, there is no code difference between 220&221
and not with 2.13?