Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wxExecute() fixes and doc updates: the return value for sync exec case is now

Browse Source 
the exit code of the process and not its pid. Warning: MSW code is untested.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@1712 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
1999-02-17 21:04:47 +00:00
parent 220a0f42d4
commit e6045e08ed
4 changed files with 102 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/latex/wx/function.tex
View File

@@ -946,9 +946,13 @@ arguments, terminated by NULL.
If {\it sync} is FALSE (the default), flow of control immediately returns.
If TRUE, the current application waits until the other program has terminated.
The return value is the process id, not the exit code of invoked program (for
this you should use wxProcess). A zero value indicates that the command could
not be executed.
In the case of synchronous execution, the return value is trhe exit code of
the process (which terminates by the moment the function returns) and will be
$-1$ if the process couldn't be started and typically 0 if the process
terminated successfully.
For asynchronous execution, however, the return value is the process id and
zero value indicates that the command could not be executed.
If callback isn't NULL and if execution is asynchronous (note that callback
parameter can not be non NULL for synchronous execution),