added wxEXEC_BLOCK flag (patch 1620430)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@45325 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -79,6 +79,7 @@ All:
|
||||
- Added wxMutex::LockTimeout() (Aleksandr Napylov)
|
||||
- Added wxMemoryInputStream(wxInputStream&) ctor (Stas Sergeev)
|
||||
- Implemented wxMemoryInputStream::CanRead()
|
||||
- Added wxEXEC_BLOCK flag (Hank Schultz)
|
||||
|
||||
All (GUI):
|
||||
|
||||
|
@@ -647,6 +647,13 @@ needed). Calling \helpref{wxKill}{wxkill} passing wxKILL\_CHILDREN will
|
||||
kill this process as well as all of its children (except those which have
|
||||
started their own session).
|
||||
|
||||
The {\tt wxEXEC\_NOEVENTS} flag prevents processing of any events from taking
|
||||
place while the child process is running. It should be only used for very
|
||||
short-lived processes as otherwise the application windows risk becoming
|
||||
unresponsive from the users point of view. As this flag only makes sense with
|
||||
{\tt wxEXEC\_SYNC}, {\tt wxEXEC\_BLOCK} equal to the sum of both of these flags
|
||||
is provided as a convenience.
|
||||
|
||||
Finally, you may use the third overloaded version of this function to execute
|
||||
a process (always synchronously, the contents of \arg{flags} is or'd with
|
||||
\texttt{wxEXEC\_SYNC}) and capture its output in the array \arg{output}. The
|
||||
|
Reference in New Issue
Block a user