summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqprocess.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqprocess.3qt')
-rw-r--r--doc/man/man3/tqprocess.3qt28
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/man/man3/tqprocess.3qt b/doc/man/man3/tqprocess.3qt
index 24eb27ca3..d6094baee 100644
--- a/doc/man/man3/tqprocess.3qt
+++ b/doc/man/man3/tqprocess.3qt
@@ -22,19 +22,19 @@ Inherits TQObject.
.BI "\fBQProcess\fR ( const TQString & arg0, TQObject * parent = 0, const char * name = 0 )"
.br
.ti -1c
-.BI "\fBQProcess\fR ( const QStringList & args, TQObject * parent = 0, const char * name = 0 )"
+.BI "\fBQProcess\fR ( const TQStringList & args, TQObject * parent = 0, const char * name = 0 )"
.br
.ti -1c
.BI "\fB~QProcess\fR ()"
.br
.ti -1c
-.BI "QStringList \fBarguments\fR () const"
+.BI "TQStringList \fBarguments\fR () const"
.br
.ti -1c
.BI "void \fBclearArguments\fR ()"
.br
.ti -1c
-.BI "virtual void \fBsetArguments\fR ( const QStringList & args )"
+.BI "virtual void \fBsetArguments\fR ( const TQStringList & args )"
.br
.ti -1c
.BI "virtual void \fBaddArgument\fR ( const TQString & arg )"
@@ -55,13 +55,13 @@ Inherits TQObject.
.BI "int \fBcommunication\fR () const"
.br
.ti -1c
-.BI "virtual bool \fBstart\fR ( QStringList * env = 0 )"
+.BI "virtual bool \fBstart\fR ( TQStringList * env = 0 )"
.br
.ti -1c
-.BI "virtual bool \fBlaunch\fR ( const TQString & buf, QStringList * env = 0 )"
+.BI "virtual bool \fBlaunch\fR ( const TQString & buf, TQStringList * env = 0 )"
.br
.ti -1c
-.BI "virtual bool \fBlaunch\fR ( const QByteArray & buf, QStringList * env = 0 )"
+.BI "virtual bool \fBlaunch\fR ( const QByteArray & buf, TQStringList * env = 0 )"
.br
.ti -1c
.BI "bool \fBisRunning\fR () const"
@@ -254,7 +254,7 @@ Constructs a QProcess with \fIarg0\fR as the command to be executed. The \fIpare
The process is not started. You must call start() or launch() to start the process.
.PP
See also setArguments(), addArgument(), and start().
-.SH "QProcess::QProcess ( const QStringList & args, TQObject * parent = 0, const char * name = 0 )"
+.SH "QProcess::QProcess ( const TQStringList & args, TQObject * parent = 0, const char * name = 0 )"
Constructs a QProcess with \fIargs\fR as the arguments of the process. The first element in the list is the command to be executed. The other elements in the list are the arguments to this command. The \fIparent\fR and \fIname\fR parameters are passed to the TQObject constructor.
.PP
The process is not started. You must call start() or launch() to start the process.
@@ -276,16 +276,16 @@ The first element in the list of arguments is the command to be executed; the fo
See also arguments() and setArguments().
.PP
Example: process/process.cpp.
-.SH "QStringList QProcess::arguments () const"
+.SH "TQStringList QProcess::arguments () const"
Returns the list of arguments that are set for the process. Arguments can be specified with the constructor or with the functions setArguments() and addArgument().
.PP
Note that if you want to iterate over the list, you should iterate over a copy, e.g.
.PP
.nf
.br
- QStringList list = myProcess.arguments();
+ TQStringList list = myProcess.arguments();
.br
- QStringList::Iterator it = list.begin();
+ TQStringList::Iterator it = list.begin();
.br
while( it != list.end() ) {
.br
@@ -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, QStringList * env = 0 )\fC [virtual]\fR"
+.SH "bool QProcess::launch ( const QByteArray & 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.
@@ -364,7 +364,7 @@ You can call this function even when a process that was started with this instan
The object emits the signal launchFinished() when this function call is finished. If the start was successful, this signal is emitted after all the data has been written to standard input. If the start failed, then this signal is emitted immediately.
.PP
See also start() and launchFinished().
-.SH "bool QProcess::launch ( const TQString & buf, QStringList * env = 0 )\fC [virtual]\fR"
+.SH "bool QProcess::launch ( const TQString & buf, TQStringList * env = 0 )\fC [virtual]\fR"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
The data \fIbuf\fR is written to standard input with writeToStdin() using the TQString::local8Bit() representation of the strings.
@@ -432,7 +432,7 @@ Note that this signal is only emitted when there is new data and not when there
See also readStdout(), readLineStdout(), and readyReadStderr().
.PP
Example: process/process.cpp.
-.SH "void QProcess::setArguments ( const QStringList & args )\fC [virtual]\fR"
+.SH "void QProcess::setArguments ( const TQStringList & args )\fC [virtual]\fR"
Sets \fIargs\fR as the arguments for the process. The first element in the list is the command to be executed. The other elements in the list are the arguments to the command. Any previous arguments are deleted.
.PP
QProcess does not perform argument substitutions; for example, if you specify "*" or "$DISPLAY", these values are passed to the process literally. If you want to have the same behavior as the shell provides, you must do the substitutions yourself; i.e. instead of specifying a "*" you must specify the list of all the filenames in the current directory, and instead of "$DISPLAY" you must specify the value of the environment variable \fCDISPLAY\fR.
@@ -454,7 +454,7 @@ Sets \fIdir\fR as the working directory for processes. This does not affect runn
Setting the working directory is especially useful for processes that try to access files with relative paths.
.PP
See also workingDirectory() and start().
-.SH "bool QProcess::start ( QStringList * env = 0 )\fC [virtual]\fR"
+.SH "bool QProcess::start ( TQStringList * env = 0 )\fC [virtual]\fR"
Tries to run a process for the command and arguments that were specified with setArguments(), addArgument() or that were specified in the constructor. 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 stringlist are interpreted as environment setttings of the form \fCkey=value\fR and the process is started in 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; under Windows the same applies for the environment variable \fCPATH\fR.