diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-02-01 15:13:01 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-02-01 15:13:01 -0600 |
| commit | deac2ca49faed824fe83066080714eb6d653615b (patch) | |
| tree | 8b5bf97c5acaaf5285985b87fa76dbea0f35e4fa /dcop | |
| parent | 0c9d97065a3d6ceb12d687555a1a33d90db96238 (diff) | |
| download | tdelibs-deac2ca49faed824fe83066080714eb6d653615b.tar.gz tdelibs-deac2ca49faed824fe83066080714eb6d653615b.zip | |
Rename a number of classes to enhance compatibility with KDE4
Diffstat (limited to 'dcop')
| -rw-r--r-- | dcop/HOWTO | 6 | ||||
| -rw-r--r-- | dcop/Mainpage.dox | 6 |
2 files changed, 6 insertions, 6 deletions
diff --git a/dcop/HOWTO b/dcop/HOWTO index 5927f3716..7126d3c1d 100644 --- a/dcop/HOWTO +++ b/dcop/HOWTO @@ -309,8 +309,8 @@ in that case the signal connection will always be deleted. A receiver can create a non-volatile connection while the sender doesn't (yet) exist. An anonymous DCOP connection should always be non-volatile. -The following example shows how KLauncher emits a signal whenever it notices -that an application that was started via KLauncher terminates. +The following example shows how TDELauncher emits a signal whenever it notices +that an application that was started via TDELauncher terminates. QByteArray params; QDataStream stream(params, IO_WriteOnly); @@ -319,7 +319,7 @@ that an application that was started via KLauncher terminates. The task manager of the TDE panel connects to this signal. It uses an anonymous connection (it doesn't require that the signal is being emitted -by KLauncher) that is non-volatile: +by TDELauncher) that is non-volatile: connectDCOPSignal(0, 0, "clientDied(pid_t)", "clientDied(pid_t)", false); diff --git a/dcop/Mainpage.dox b/dcop/Mainpage.dox index 423571280..62fd3cf44 100644 --- a/dcop/Mainpage.dox +++ b/dcop/Mainpage.dox @@ -541,8 +541,8 @@ in that case the signal connection will always be deleted. A receiver can create a non-volatile connection while the sender doesn't (yet) exist. An anonymous DCOP connection should always be non-volatile. -The following example shows how KLauncher emits a signal whenever it notices -that an application that was started via KLauncher terminates: +The following example shows how TDELauncher emits a signal whenever it notices +that an application that was started via TDELauncher terminates: \code QByteArray params; @@ -553,7 +553,7 @@ kapp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); The task manager of the Trinity panel connects to this signal. It uses an anonymous connection (it doesn't require that the signal is being emitted -by KLauncher) that is non-volatile: +by TDELauncher) that is non-volatile: \code connectDCOPSignal(0, 0, "clientDied(pid_t)", "clientDied(pid_t)", false); |