Archive: ExecShell


ExecShell
I've been using NSIS for ages now, but I have failed to be able to use ExecShell.
I'm trying to get it to open up .zip files, but it won't do it.

ExecShell "$3\$2" SW_SHOWNORMAL


The file it is targeting is correct.
What am I doing wrong?

-Stu


Try

ExecShell open "$3\$2" SW_SHOWNORMAL


Thanks it worked.
I'm trying to get the program now to go in a loop, so that when the user clicks Next on the last page, he is directed to the First page of the program.
Is there a way to do this with 2.0b3, or would I need to download the latest cvs version?

-Stu


Are you writing an installer of something else? NSIS just works like a normal wizard, so that's not possible with normal pages.

A possibility is to use InstallOptions for all pages and call the InstallOptions commands in a loop. Or you can launch your application again when it's finished.


Since my program takes ages to load up (it downloads a list of updates, puts them into a drop list, filters them and so on) I resorted to this:

When the user clicks next on the final page, it will write "1" to an ini string, runs itself again, and then quits.
On the oninit function, I simply check if the figure is "1" in the ini file, and if it is "1" then it skips all of the oninit function and loads up the first page immediatly as if it just went back.

It would be nice to have a command like this:
GotoPage x

Where x is the Page order in order of Page commands.

-Stu


Yes, all pages are IO pages, so that might be a possibility.
I want it split into different pages right now, since each page has lots of things built into them.

I'll get back onto it tomorrow.

-Stu


Ok. I now have 1 single page function full of all the different IO pages. Now, however, it compiles it thinking that because I only have 1 page, it has that one last page as the final InstFiles page (It's an IO page, but its treated as if it is an InstFiles page). The cancel button on it is blanked out, and I cannot get off the program. The close button in the corner just makes it move through the IO pages.

Does that mean this isn't possible.

-Stu


Add a feature request for GotoPage if it's not there yet. It'll work with the new flags optimization I am going to implement. For now you'll have to call your installer again when it's finished as been said in another post.


I resorted to having it re-open the installer on-click of the Next button.

-Stu