From 34adc693b0bd700af0a76f41a5bbc490bcdcc54d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Karsten=20Ball=C3=BCder?= Date: Thu, 15 Apr 1999 14:40:41 +0000 Subject: [PATCH] Added a wxYield() warning to wxExecute() entry. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@2179 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/latex/wx/function.tex | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/latex/wx/function.tex b/docs/latex/wx/function.tex index 88b47f7324..ee1ed4a498 100644 --- a/docs/latex/wx/function.tex +++ b/docs/latex/wx/function.tex @@ -1058,7 +1058,10 @@ If TRUE, the current application waits until the other program has terminated. 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. +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 simples case by +calling \helpref{wxEnableTopLevelWindows(FALSE)}{wxenabletoplevelwindows}. For asynchronous execution, however, the return value is the process id and zero value indicates that the command could not be executed. -- 2.47.2