t_vgemert
17th February 2003 16:09 UTC

Close compiler window
Hi,

I were wondering if it is possible to let the compiler window autoclose?
This is because I am using the makensisw.exe in one of my (macromedia) Director presentations to create a modified *.nsi file on the fly and compiling it, so the director movie calls
'makensisw.exe c:\install.exe c:\file.nsi'. If the compiler can perform an autoclose I could detect the presence (or not!) of the makensisw.exe window and SO.... detect if it is still active or not!

Peace...

Tom van Gemert
Trimedia Interactive Projects
Eindhoven, The Netherlands
www.trimedia.nl

Sunjammer
17th February 2003 16:51 UTC

Why don't you just use makensis.exe directly instead of makensisw.exe?

t_vgemert
18th February 2003 14:48 UTC

Could do that... but still

Joost Verburg
18th February 2003 15:11 UTC

What is the problem? Call makensis.exe instead of makensisw.exe.

Sunjammer
18th February 2003 15:19 UTC

t_vgemert: Just to clarify, makensisw is just a thin wrapper around makensis, all of the real compilation is done by makensis. In fact makensisw never used to exist!

So, if you are doing compilation from a script or wherever you should *not* be invoking makensisw, you should be invoking makensis.exe.

If you still want to use makensisw can you please explain why, I (and doubtless Joost will say the same) have absolutely no idea why you would want to invoke makensisw.exe instead.

t_vgemert
19th February 2003 08:21 UTC

Ok, understand that. I wanted to use makensisw because it has a GUI, but still that would be a temporary solution for me because in the end I need to compile the nsi file in the background while the user gets a progress/busy dialogue. But if the makensisw.exe had a function which makes its window close after completion it would be a nice temporary solution for me.

Sunjammer
19th February 2003 09:12 UTC

Have you tried sending a WM_CLOSE message to makensisw? try looking at this.

Joost Verburg
19th February 2003 13:11 UTC

If you close makensisw immidiately, why do you need the GUI?

t_vgemert
19th February 2003 13:48 UTC

Smart one Joost! In my final version I don't need the GUI but as I reach my deadline on this project I realy like to have an alternative solution ready, so the makensisw.exe that closes by itself is a nice compromise ain't it.

t_vgemert
19th February 2003 13:49 UTC

And it doesn't close immediately. My nsi file takes about 1 - 3 minutes to compile because of big files...

Sunjammer
19th February 2003 13:51 UTC

Use nsExec::ExecToLog, that way you will know when it finishes, you won't have an external window, and you will capture the build output as makensisw does.

Joost Verburg
19th February 2003 15:02 UTC

He is not calling it using NSIS. But if you don't use any of the MakeNSISW functions, why not call makensis.exe? It will show you a console window instead of the GUI.

Sunjammer
19th February 2003 15:28 UTC

Oh yeah, sorry :)