Archive: Dumb question ... (newbie)


Just a quick query, that I can't see in the documentation.

It is to do with installers built with installation options, for example the example2.nsi in the distribution.

When this installer is running, the first step that a user completes is to make a selection, in this case whether to select Start Menu Shortcuts or not.

The user then selects next and is taken to the Installation Directory screen.

If at this point he wishes to change his selection, he clicks back.

But when the first screen, entitled Installation Options shows, the Start Menu Shortcusts shows as selected again.

The installer appears to have forgotten what had been chosen.

Is there any way of making it remember ?


Not with the current code, but I don't personally consider that a "dumb" question. It should be, at the very least, up to the developer whether or not the options go back to default. I hereby request a new "feature" for NSIS (Edgewise and Justin take note :) )...


OptionsReset ON|OFF


OptionsReset ON will make the options jump back to the developer configured defaults if the user selects back.

OptionsReset OFF will let the user-selected options stay if the user backs up to check what they did.

-=Gonzotek=-

;>

Hrm. It really ought to remember user settings by default. I'll see what I can do about that.

If the user enters a change and hits the Next button, I can't imagine why it should ever reset to the developer's settings. I don't think that such an option is necessary.


Thanks :)


Thanks guys ...

I'd just like to say that effort on this installer is fantastic.

I downloaded nsis143.exe to build an installer for use in our company, finished it in 2 hrs, and started the documentation for it in the pm.

When I checked out the web site to ensure the URLs were right in the afternoon, a new version had appeared ...

I suppose I prefixed the question with newbie as I'd got less than 8hrs experience with it, and thought it was a silly question.

Anyway, thanks for your input, hard work and help.

regards

tim


I fixed this problem in my non-official version, 1.44e... I'll do a binary-only release this afternoon, and a full source release ASAP.

Kudos to Justin for creating such a wonderful installer and open-sourcing the code :)