🚀 go-pugleaf

Thanks Remy,

> You should be using CreateProcess() instead.
   I did, works fine now.
   However, how can I hide the DOS window?
   (Probably via STARTUPINFO, but I can't figure out how)

> You should not be using TerminateProcess()
    I have to I think. It is a console app with no windowhandle to go after.

> Why are you not letting the process terminate itself normally?
    It does not. It's a 3rd party app that terminates itself only if
    unaltered information appears after a certain period of time)

> Use GetExitCodeProcess().
   That does it.

Wiebe

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> schreef in bericht 
news:441e0231$1@newsgroups.borland.com...
>
> "Wiebe Vos" <wiebe@foxware.nl> wrote in message
> news:441dc83a@newsgroups.borland.com...
>
>> I launch a (console) app via ShellExecuteEx()
>
> You should be using CreateProcess() instead.  Don't use ShellExecute/Ex() 
> to
> lanch .exe files directly.  You should only use it to launch data files 
> when
> you don't know ahead of time which .exe will open them.
>
>> and use the hProcess handle in SHELLEXECUTEINFO to
>> terminate it later via TerminateProcess().
>
> You should not be using TerminateProcess() at all, unless absolutely
> necessary.  TerminateProcess() is a brute-force termination.  Why are you
> not letting the process terminate itself normally?
>
>> How can I check in the meantime if the app is still running
>> and not been terminated by someone else?
>
> Use GetExitCodeProcess().
>
>
> Gambit
>
>
>