diff options
Diffstat (limited to 'doc/man/man3/tqprocess.3qt')
| -rw-r--r-- | doc/man/man3/tqprocess.3qt | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/man/man3/tqprocess.3qt b/doc/man/man3/tqprocess.3qt index 64da05ae3..0e2fe3009 100644 --- a/doc/man/man3/tqprocess.3qt +++ b/doc/man/man3/tqprocess.3qt @@ -61,7 +61,7 @@ Inherits TQObject. .BI "virtual bool \fBlaunch\fR ( const TQString & buf, TQStringList * env = 0 )" .br .ti -1c -.BI "virtual bool \fBlaunch\fR ( const QByteArray & buf, TQStringList * env = 0 )" +.BI "virtual bool \fBlaunch\fR ( const TQByteArray & buf, TQStringList * env = 0 )" .br .ti -1c .BI "bool \fBisRunning\fR () const" @@ -73,10 +73,10 @@ Inherits TQObject. .BI "int \fBexitStatus\fR () const" .br .ti -1c -.BI "virtual QByteArray \fBreadStdout\fR ()" +.BI "virtual TQByteArray \fBreadStdout\fR ()" .br .ti -1c -.BI "virtual QByteArray \fBreadStderr\fR ()" +.BI "virtual TQByteArray \fBreadStderr\fR ()" .br .ti -1c .BI "bool \fBcanReadLineStdout\fR () const" @@ -103,7 +103,7 @@ Inherits TQObject. .BI "void \fBkill\fR () const" .br .ti -1c -.BI "virtual void \fBwriteToStdin\fR ( const QByteArray & buf )" +.BI "virtual void \fBwriteToStdin\fR ( const TQByteArray & buf )" .br .ti -1c .BI "virtual void \fBwriteToStdin\fR ( const TQString & buf )" @@ -137,7 +137,7 @@ You can write to the started program's standard input, and can read the program' .PP There are two different ways to start a process. If you just want to run a program, optionally passing data to its standard input at the beginning, use one of the launch() functions. If you want full control of the program's standard input (especially if you don't know all the data you want to send to standard input at the beginning), use the start() function. .PP -If you use start() you can write to the program's standard input using writeToStdin() and you can close the standard input with closeStdin(). The wroteToStdin() signal is emitted if the data sent to standard input has been written. You can read from the program's standard output using readStdout() or readLineStdout(). These functions return an empty QByteArray if there is no data to read. The readyReadStdout() signal is emitted when there is data available to be read from standard output. Standard error has a set of functions that correspond to the standard output functions, i.e. readStderr(), readLineStderr() and readyReadStderr(). +If you use start() you can write to the program's standard input using writeToStdin() and you can close the standard input with closeStdin(). The wroteToStdin() signal is emitted if the data sent to standard input has been written. You can read from the program's standard output using readStdout() or readLineStdout(). These functions return an empty TQByteArray if there is no data to read. The readyReadStdout() signal is emitted when there is data available to be read from standard output. Standard error has a set of functions that correspond to the standard output functions, i.e. readStderr(), readLineStderr() and readyReadStderr(). .PP If you use one of the launch() functions the data you pass will be sent to the program's standard input which will be closed once all the data has been written. You should \fInot\fR use writeToStdin() or closeStdin() if you use launch(). If you need to send data to the program's standard input after it has started running use start() instead of launch(). .PP @@ -348,7 +348,7 @@ This tries to terminate the process the nice way. If the process is still runnin The slot returns immediately: it does not wait until the process has finished. When the process terminates, the processExited() signal is emitted. .PP See also tryTerminate() and processExited(). -.SH "bool QProcess::launch ( const QByteArray & buf, TQStringList * env = 0 )\fC [virtual]\fR" +.SH "bool QProcess::launch ( const TQByteArray & buf, TQStringList * env = 0 )\fC [virtual]\fR" Runs the process and writes the data \fIbuf\fR to the process's standard input. If all the data is written to standard input, standard input is closed. The command is searched for in the path for executable programs; you can also use an absolute path in the command itself. .PP If \fIenv\fR is null, then the process is started with the same environment as the starting process. If \fIenv\fR is non-null, then the values in the string list are interpreted as environment setttings of the form \fCkey=value\fR and the process is started with these environment settings. For convenience, there is a small exception to this rule under Unix: if \fIenv\fR does not contain any settings for the environment variable \fCLD_LIBRARY_PATH\fR, then this variable is inherited from the starting process. @@ -404,16 +404,16 @@ Reads a line of text from standard output, excluding any trailing newline or car By default, the text is interpreted to be in Latin-1 encoding. If you need other codecs, you can set a different codec with TQTextCodec::setCodecForCStrings(). .PP See also canReadLineStdout(), readyReadStdout(), readStdout(), and readLineStderr(). -.SH "QByteArray QProcess::readStderr ()\fC [virtual]\fR" +.SH "TQByteArray QProcess::readStderr ()\fC [virtual]\fR" Reads the data that the process has written to standard error. When new data is written to standard error, the class emits the signal readyReadStderr(). .PP -If there is no data to read, this function returns a QByteArray of size 0: it does not wait until there is something to read. +If there is no data to read, this function returns a TQByteArray of size 0: it does not wait until there is something to read. .PP See also readyReadStderr(), readLineStderr(), readStdout(), and writeToStdin(). -.SH "QByteArray QProcess::readStdout ()\fC [virtual]\fR" +.SH "TQByteArray QProcess::readStdout ()\fC [virtual]\fR" Reads the data that the process has written to standard output. When new data is written to standard output, the class emits the signal readyReadStdout(). .PP -If there is no data to read, this function returns a QByteArray of size 0: it does not wait until there is something to read. +If there is no data to read, this function returns a TQByteArray of size 0: it does not wait until there is something to read. .PP See also readyReadStdout(), readLineStdout(), readStderr(), and writeToStdin(). .PP @@ -478,7 +478,7 @@ See also kill() and processExited(). Returns the working directory that was set with setWorkingDirectory(), or the current directory if none has been explicitly set. .PP See also setWorkingDirectory() and QDir::current(). -.SH "void QProcess::writeToStdin ( const QByteArray & buf )\fC [virtual slot]\fR" +.SH "void QProcess::writeToStdin ( const TQByteArray & buf )\fC [virtual slot]\fR" Writes the data \fIbuf\fR to the process's standard input. The process may or may not read this data. .PP This function always returns immediately. The data you pass to writeToStdin() is copied into an internal memory buffer in QProcess, and when control goes back to the event loop, QProcess will starting transferring data from this buffer to the running process. Sometimes the data will be transferred in several payloads, depending on how much data is read at a time by the process itself. When QProcess has transferred all the data from its memory buffer to the running process, it emits wroteToStdin(). |