Progressbar for extraction

JockeL · 16th September 2008, 15:09

Hi all!

We only use the NSIS compiler as to package our own installation in an easy way for our customers. We have used this solution for quite some time but I myself am completely new to working with NSIS.

So far NSIS has been run in silentmode and just executed our setup.exe installer which runs in normal mode (not silent). However now we have packages that are up to 200-400 mb and in silent mode it looks to the customer as though nothing is happening when we extract the files in silent mode.

I have been trying to just include the MUI_PAGE_INSTFILES which shows the progressbar fine but when our executable is called this dialog doesn't close but is still shown behind.

All help appreciated
/Joakim

kichik · 16th September 2008, 16:58

Doesn't close after the installation is done? Use SetAutoClose or AutoCloseWindow.

JockeL · 17th September 2008, 11:24

Thank you for your response.

I would like the dialog to close as soon as extraction is done, I do not want it to wait for our executable to be closed as our installer has its own dialogs and this might be confusing for the end user.

Comperio · 17th September 2008, 19:25

hmm... are you maybe using ExecWait to launch the 2nd installation? If so, try using just Exec.

JockeL · 18th September 2008, 09:36

Thank you for your response again!

Maybe i wasn't being clear and for that I apologize but I am very new to using NSIS.

We are currently using ExecWait and if we use Exec instead this solves our problem. However we also would like the extraction folder to be deleted upon completion of the installer and currently delete the output folder when installation is done.

This is only possible by using ExecWait as far as I know. So the scenario we would like to achieve is a scenario where the extraction dialog closes upon completion of the extraction but the excraction folder containing our installer files will not be removed until the installer is finished.

I will attach my project and appreciate all help I can get.

demiller9 · 18th September 2008, 14:10

I think you should continue to use ExecWait so that you can delete the extraction folder after the installer completes. While the installer is running you can hide the wrapper program that extracted it.

code:
!include WinMessages.nsh

GetDlgItem $0 $HWNDPARENT 1

ShowWindow $0 ${SW_HIDE}

16th September 2008, 15:09	#1
JockeL Junior Member Join Date: Sep 2008 Posts: 3	Progressbar for extraction Hi all! We only use the NSIS compiler as to package our own installation in an easy way for our customers. We have used this solution for quite some time but I myself am completely new to working with NSIS. So far NSIS has been run in silentmode and just executed our setup.exe installer which runs in normal mode (not silent). However now we have packages that are up to 200-400 mb and in silent mode it looks to the customer as though nothing is happening when we extract the files in silent mode. I have been trying to just include the MUI_PAGE_INSTFILES which shows the progressbar fine but when our executable is called this dialog doesn't close but is still shown behind. All help appreciated /Joakim

16th September 2008, 16:58	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Doesn't close after the installation is done? Use SetAutoClose or AutoCloseWindow. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

18th September 2008, 14:10	#6
demiller9 Senior Member Join Date: Mar 2006 Location: Dallas Posts: 462	I think you should continue to use ExecWait so that you can delete the extraction folder after the installer completes. While the installer is running you can hide the wrapper program that extracted it. code: !include WinMessages.nsh GetDlgItem $0 $HWNDPARENT 1 ShowWindow $0 ${SW_HIDE}

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

17th September 2008, 11:24	#3
JockeL Junior Member Join Date: Sep 2008 Posts: 3	Thank you for your response. I would like the dialog to close as soon as extraction is done, I do not want it to wait for our executable to be closed as our installer has its own dialogs and this might be confusing for the end user.

17th September 2008, 19:25	#4
Comperio Major Dude Join Date: Jan 2005 Location: Oregon Coast Posts: 737	hmm... are you maybe using ExecWait to launch the 2nd installation? If so, try using just Exec.