Przemysław Czerpak wrote:
>
> Look at parameters. They give you the answer.
> To set <cStdOut>, <cStdErr> and <nResult> is necessary to wait inside
> hb_processRun() until executed command terminates.
>
> If you want to still execute your foreground process then use:
> hb_processOpen( <cCommand>, ;
> [ @<hStdIn> ], [ @<hStdOut> ], [ @<hStdErr> ], ;
> [ <lDetach> ], [ @<nPID> ] ) -> <hProcess> | F_ERROR
> and then:
> hb_processValue( <hProcess> [, <lWait=.T.> ] ) -> <nResult>
> or:
> hb_processClose( <hProcess> [, <lGentle=.T.> ] ) -> <lTerminated>
>
> <hStdIn>, <hStdOut> and <hStdErr are file handles from which you can
> read and write using FREAD()/FWRITE().
> <nResult> is value returned by executed process (errorLevel()),
> <lWait> is .T. by default,
> <lGentle> is .T. by default, when it's .F. the process is killed
> unconditionally.
>
I tried this:
hb_processRun( cExecutable, NIL, NIL, NIL, .F. )
Executable is invoked but control is returned to the caller after
termination of executable.
hb_processRun( cExecutable, NIL, NIL, NIL, .T. )
Executable is active without showing up interface ( as a daemon )
but still control is not returned back to caller, hangs forever and has to
be killed via task manager.
I need a functionality where new process executes normally at its own and
control is returned back to caller. How this can be achieved with
hb_processRun() ?
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://n2.nabble.com/HBIDE-Project-build-start-folder-problem-tp4861627p4894704.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
