two installer bugs w. 1.92.1

[akahige]

I've done two separate installs of 1.92.1 in the last couple of days and noticed this problem on both setups.

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

The other thing that I noticed, on that same configuration panel is that even though I had selected the shell extension in the list of options to be installed, the box to actually *use* the shell extension was greyed out as if it had not been installed and was therefore unavailable for selection here. An additional peculiar thing is that it turned out that the shell extension had been installed and was functional.

I did a search on the forums and couldn't find anyone reporting anything like this, so if there's anything that I can do to help troubleshoot it, let me know.

[xnview]

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

Ok, i'll check

The other thing that I noticed, on that same configuration panel is that even though I had selected the shell extension in the list of options to be installed, the box to actually *use* the shell extension was greyed out as if it had not been installed and was therefore unavailable for selection here. An additional peculiar thing is that it turned out that the shell extension had been installed and was functional.

You have installed the full setup & shell extension, right?

[akahige]

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

Ok, i'll check

Since posting this, I noticed something else interesting. When I dumped a preconfigured INI file into the $profile directory and fired XnView back up, it seems to have noticed the INI path wasn't correct and it moved the INI to the app install directory.

The other thing that I noticed, on that same configuration panel is that even though I had selected the shell extension in the list of options to be installed, the box to actually *use* the shell extension was greyed out as if it had not been installed and was therefore unavailable for selection here. An additional peculiar thing is that it turned out that the shell extension had been installed and was functional.

You have installed the full setup & shell extension, right?

Yes, that's right. Using the full setup file and check the "shell extension" option which is not automatically selected by the installer.

[xnview]

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

Ok, i'll check

Since posting this, I noticed something else interesting. When I dumped a preconfigured INI file into the $profile directory and fired XnView back up, it seems to have noticed the INI path wasn't correct and it moved the INI to the app install directory.

Yes right, must not be like that. If you have the setup, xnview must not check if there is a good .ini somewhere....

[XnTriq]

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

To make the setting (Save Options as INI in folder XnView) become effective you'll have to restart XnView.

Maybe a little hint would be in order:

1. Interface » Interface » Windows » Use XP style menus » Pop-up: “You must restart XnView.”
2. Browser » Folder tree » Use label in tab (please restart the browser)

Related discussions:

• REQ: INI file in XnView folder - for USB stick
• Why is there a XnView folder under %appdata%
• Save relative files at XnView folder
• How Can I Relocate my xnview.ini File off my C Drive
• Can an option be turned on at installation?

[akahige]

Once the installation is complete, there is a panel that comes up asking where the .INI should be stored. In both cases, I selected the installation directory, however, when XnView was first launched, the default INI file was created in $profile.

To make the setting (Save Options as INI in folder XnView) become effective you'll have to restart XnView.

Maybe a little hint would be in order:

1. Interface » Interface » Windows » Use XP style menus » Pop-up: “You must restart XnView.”
2. Browser » Folder tree » Use label in tab (please restart the browser)

The problem that I have with that logic is that this isn't a change in configuration -- which would make sense that you'd have to restart the app -- the problem here is that XnView isn't running, hasn't ever run, and can't manage to get its config straight without running, not once but apparently twice. Does that make sense? (I mean, does what I'm saying make sense, not does it make sense programatically?) This isn't a change from a preexisting configuration, this is XnView asking how it should initially configure itself. Is there a technical reason for this behavior? (At this point, I"m just curious since I understand that this isn't a bug but rather XnView's expected behavior.)

In a related thought, any confusion about where, what, and when XnView does anything with its configuration files would be totally moot if there was an import/export feature. I see that that topic has come up on the forum only a few times, and only really addressed in terms of describing where the configuration files are stored and what it takes to hunt them down. Is an import/export feature something worth considering? It would certainly be nice from the standpoint of userfriendliness...

[XnTriq]

If you start XnView v1.93 for the first time and select the Use .ini file in Application folder (Single-User system) option in the Configuration Wizard, the setting will take effect immidiately.

[akahige]

Sounds cool! When is v1.93 going to be available for public consumption?

[XnTriq]

Announcement: XnView 1.93

[akahige]

Gotcha. I had popped by the download page but it still listed 1.92.1. Must be a caching issue. I'll be checking it out forthwith!

Thanks!