Hello NSIS-community,
When given a certain parameter (i.e. /wait) on the command line, I want my installer to wait for some process to close down. This process hasn't been started by the installer, so ExecWait is not an option. Also, I'm only concerned about waiting for it to close - I don't need to initiate the closing. Once this external process has closed down, I need the installation of files to continue without user interaction.
Currently, I'm doing this in the Show callback of the InstFiles page. Using the Processes plugin, I can look for the process. If I don't find it, all is fine and dandy and I can continue. But if I do find it, I need to wait some more for it to finish. However, when using Sleep (i.e. 50ms), the user interface locks up, and since I am still in the Show callback, the InstFiles page isn't even fully painted yet.
So, how can this be done sensibly? The installation is part of an automatic updating for *very* non-technical users. So it can be thought of as "passive" yet "attended". It must not look "broken" while waiting for the process. An added bonus would be, that the waiting is abortable ... by which the whole installation will be aborted.
waiting for another process to close
2 posts