XnView Software

I just updated from XnView 2.36 to v 2.39 (extended version). I have a Win 7 system w/ 16GB RAM. I just installed the updated app over the current installation--making no changes.

I have several custom entries in the thumbnail labels and when I opened the updated application and opened some images, the thumbnail info has been trashed! The custom lines were wiped out and other entries were truncated. I closed the XnView application and rebooted my system, thinking that it might solve the situation. No luck there--when I reopened the application, the same situation existed!

1] What caused it?
2} How can I avoid it in the future?.

Thanks for any help you can give.

Steve Bonrepos

Welcome totthe forum, Steve Bonrepos.

I can confirm that something must have changed. When I copied & pasted my custom labels from an old xnview.ini (v1.99)…
… to the INI of XnView v2.39 and restarted the program, the bullet signs (Alt+0149) were displayed as question marks.

When this happened to me, I had only installed the new version by double-clicking on the downloaded file's icon; I did nothing involving the .ini file. (I was not aware of a need for any action involving the .ini file.)

Since I have the contents of all my thumbnail labels in written form, I can re-create them--however, that is an unnecessary step to be forced on me. I'd really like to have a solution so that it does not happen again.

Thanks

Steve

stevebon wrote:When this happened to me, I had only installed the new version by double-clicking on the downloaded file's icon; I did nothing involving the .ini file. (I was not aware of a need for any action involving the .ini file.)

Manually editing xnview.ini is — if at all — rarely required. I'm usually downloading the ZIP package (no setup) of new versions. After completing the basic configuration of v2.39, I copied my customized labels from the INI of a very old version so I wouldn't have to type it all in. That's when I ran into an issue which seemed to be related to the one you describe. Unfortunately, I haven't been able to reproduce it since.