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

added wxEXEC_NODISABLE

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@31081 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2004-12-19 23:59:28 +00:00
parent de9815cb4f
commit f38f689990
5 changed files with 32 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -553,9 +553,12 @@ In the case of synchronous execution, the return value is the 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. Also, while waiting for the process to
terminate, wxExecute will call \helpref{wxYield}{wxyield}. The caller
should ensure that this can cause no recursion, in the simplest case by
calling \helpref{wxEnableTopLevelWindows(false)}{wxenabletoplevelwindows}.
terminate, wxExecute will call \helpref{wxYield}{wxyield}. Because of this, by
default this function disables all application windows to avoid unexpected
reentrancies which could result from the users interaction with the program
while the child process is running. If you are sure that it is safe to not
disable the program windows, you may pass \texttt{wxEXEC\_NODISABLE} flag to
prevent this automatic disabling from happening.
For asynchronous execution, however, the return value is the process id and
zero value indicates that the command could not be executed. As an added