1. stderr redirection seems to work under Windows too (documented new
wxProcess method too) 2. don't show the window of the (console) process in wxExecute if IO is redirected 3. implemented wxColourDialog::SetTitle 4. implemented wxGauge95::SetForeground/BackgroundColour() git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_2_BRANCH@7491 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -1319,6 +1319,8 @@ wxWindows errors. See also \helpref{wxFatalError}{wxfatalerror}.
|
||||
|
||||
\func{long}{wxExecute}{\param{const wxString\& }{command}, \param{wxArrayString\& }{output}}
|
||||
|
||||
\func{long}{wxExecute}{\param{const wxString\& }{command}, \param{wxArrayString\& }{output}, \param{wxArrayString\& }{errors}}
|
||||
|
||||
Executes another program in Unix or Windows.
|
||||
|
||||
The first form takes a command string, such as {\tt "emacs file.txt"}.
|
||||
@@ -1326,8 +1328,8 @@ The first form takes a command string, such as {\tt "emacs file.txt"}.
|
||||
The second form takes an array of values: a command, any number of
|
||||
arguments, terminated by NULL.
|
||||
|
||||
The semantics of the third version is different from the first two and is
|
||||
described in more details below.
|
||||
The semantics of the third and fourth versions is different from the first two
|
||||
and is described in more details below.
|
||||
|
||||
If {\it sync} is FALSE (the default), flow of control immediately returns.
|
||||
If TRUE, the current application waits until the other program has terminated.
|
||||
@@ -1350,7 +1352,8 @@ the process finishes.
|
||||
|
||||
Finally, you may use the third overloaded version of this function to execute
|
||||
a process (always synchronously) and capture its output in the array
|
||||
{\it output}.
|
||||
{\it output}. The fourth version adds the possibility to additionally capture
|
||||
the messages from standard error output in the {\it errors} array.
|
||||
|
||||
See also \helpref{wxShell}{wxshell}, \helpref{wxProcess}{wxprocess},
|
||||
\helpref{Exec sample}{sampleexec}.
|
||||
|
@@ -14,6 +14,15 @@ However, if it is not processed, the object will delete itself and so the
|
||||
library users should only delete those objects whose notifications have been
|
||||
processed (and call \helpref{Detach()}{wxprocessdetach} for others).
|
||||
|
||||
wxProcess also supports IO redirection of the child process. For this, you have
|
||||
to call its \helpref{Redirect}{wxprocessredirect} method before passing it to
|
||||
\helpref{wxExecute}{wxexecute}. If the child process was launched successfully,
|
||||
\helpref{GetInputStream}{wxprocessgetinputstream},
|
||||
\helpref{GetOutputStream}{wxprocessgetoutputstream} and
|
||||
\helpref{GetErrorStream}{wxprocessgeterrorstream} can then be used to retrieve
|
||||
the streams corresponding to the child process stdandard output, input and
|
||||
error output respectively.
|
||||
|
||||
\wxheading{Derived from}
|
||||
|
||||
\helpref{wxEvtHandler}{wxevthandler}
|
||||
@@ -22,6 +31,11 @@ processed (and call \helpref{Detach()}{wxprocessdetach} for others).
|
||||
|
||||
<wx/process.h>
|
||||
|
||||
\wxheading{See also}
|
||||
|
||||
\helpref{wxExecute}{wxexecute}\\
|
||||
\helpref{exec sample}{sampleexec}
|
||||
|
||||
\latexignore{\rtfignore{\wxheading{Members}}}
|
||||
|
||||
\membersection{wxProcess::wxProcess}\label{wxprocessconstr}
|
||||
@@ -62,19 +76,26 @@ from its parent, no notification events will be sent to the parent and the
|
||||
object will delete itself upon reception of the process termination
|
||||
notification.
|
||||
|
||||
\membersection{wxProcess::GetErrorStream}\label{wxprocessgeterrorstream}
|
||||
|
||||
\constfunc{wxInputStream* }{GetErrorStream}{\void}
|
||||
|
||||
Returns an input stream which corresponds to the standard error output (stderr)
|
||||
of the child process.
|
||||
|
||||
\membersection{wxProcess::GetInputStream}\label{wxprocessgetinputstream}
|
||||
|
||||
\constfunc{wxInputStream* }{GetInputStream}{\void}
|
||||
|
||||
It returns a output stream corresponding to the input stream of the subprocess.
|
||||
If it is NULL, you have not turned on the redirection.
|
||||
It returns a output stream corresponding to the standard output stream of the
|
||||
subprocess. If it is NULL, you have not turned on the redirection.
|
||||
See \helpref{wxProcess::Redirect}{wxprocessredirect}.
|
||||
|
||||
\membersection{wxProcess::GetOutputStream}\label{wxprocessgetoutputstream}
|
||||
|
||||
\constfunc{wxOutputStream* }{GetOutputStream}{\void}
|
||||
|
||||
It returns an output stream correspoding to the output stream of the subprocess.
|
||||
It returns an output stream correspoding to the input stream of the subprocess.
|
||||
If it is NULL, you have not turned on the redirection.
|
||||
See \helpref{wxProcess::Redirect}{wxprocessredirect}.
|
||||
|
||||
|
@@ -151,6 +151,9 @@ The exec sample demonstrates the \helpref{wxExecute}{wxexecute} and
|
||||
external programs and the sample shows how to do this synchronously (waiting
|
||||
until the program terminates) or asynchronously (notification will come later).
|
||||
|
||||
It also shows how to capture the output of the child process in both
|
||||
synchronous and asynchronous cases.
|
||||
|
||||
\subsection{Scroll subwindow sample}\label{samplescrollsub}
|
||||
|
||||
This sample demonstrates the use of the \helpref{wxScrolledWindow}{wxscrolledwindow}
|
||||
|
@@ -1,14 +1,14 @@
|
||||
[OPTIONS]
|
||||
BMROOT=d:\wx2\wxWind~1\docs/latex/wx ; Assume that bitmaps are where the source is
|
||||
;BMROOT=L:\wxWindows\docs\latex\wx ; Assume that bitmaps are where the source is
|
||||
TITLE=wxWindows Manual
|
||||
CONTENTS=Contents
|
||||
COMPRESS=HIGH
|
||||
|
||||
[FILES]
|
||||
wx.rtf
|
||||
Wx.rtf
|
||||
|
||||
[CONFIG]
|
||||
CreateButton("Up", "&Up", "JumpId(`wx.hlp', `Contents')")
|
||||
CreateButton("Up", "&Up", "JumpId(`Wx.hlp', `Contents')")
|
||||
BrowseButtons()
|
||||
|
||||
[MAP]
|
||||
|
Reference in New Issue
Block a user