diff options
Diffstat (limited to 'dcop')
| -rw-r--r-- | dcop/HOWTO | 12 | ||||
| -rw-r--r-- | dcop/Mainpage.dox | 12 |
2 files changed, 12 insertions, 12 deletions
diff --git a/dcop/HOWTO b/dcop/HOWTO index 86324529f..16e60317d 100644 --- a/dcop/HOWTO +++ b/dcop/HOWTO @@ -98,7 +98,7 @@ case: * returns the appId that is actually registered, which _may_ be * different from what you passed */ -appId = client->registerAs(kApp->name()); +appId = client->registerAs(tdeApp->name()); If you never retrieve the DCOPClient pointer from TDEApplication, the object will not be created and thus there will be no memory overhead. @@ -111,8 +111,8 @@ call DCOPClient::registerAs() with the new name. TDEUniqueApplication automatically registers itself to DCOP. If you are using TDEUniqueApplication you should not attach or register yourself, this is already done. The appId is by definition -equal to kapp->name(). You can retrieve the registered DCOP client -by calling kapp->dcopClient(). +equal to tdeApp->name(). You can retrieve the registered DCOP client +by calling tdeApp->dcopClient(). Sending Data to a Remote Application: ------------------------------------- @@ -247,7 +247,7 @@ bool BarObject::process(const QCString &fun, const QByteArray &data, TQString result = self->doIt(i); DCOPClientTransaction *myTransaction; - myTransaction = kapp->dcopClient()->beginTransaction(); + myTransaction = tdeApp->dcopClient()->beginTransaction(); // start processing... // Calls slotProcessingDone when finished. @@ -266,7 +266,7 @@ slotProcessingDone(DCOPClientTransaction *myTransaction, const TQString &result) QByteArray replyData; QDataStream reply(replyData, IO_WriteOnly); reply << result; - kapp->dcopClient()->endTransaction( myTransaction, replyType, replyData ); + tdeApp->dcopClient()->endTransaction( myTransaction, replyType, replyData ); } DCOP Signals @@ -315,7 +315,7 @@ that an application that was started via TDELauncher terminates. QByteArray params; QDataStream stream(params, IO_WriteOnly); stream << pid; - kapp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); + tdeApp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); 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 diff --git a/dcop/Mainpage.dox b/dcop/Mainpage.dox index 186aed76b..ecd2b70f3 100644 --- a/dcop/Mainpage.dox +++ b/dcop/Mainpage.dox @@ -59,7 +59,7 @@ DCOPClient::registerAs(const QCString &name) to do so. In the simple case: \code -appId = client->registerAs(kapp->name()); +appId = client->registerAs(tdeApp->name()); \endcode If you never retrieve the DCOPClient pointer from TDEApplication, the @@ -73,8 +73,8 @@ call DCOPClient::registerAs() with the new name. TDEUniqueApplication automatically registers itself to DCOP. If you are using TDEUniqueApplication you should not attach or register yourself, this is already done. The appId is by definition -equal to \p kapp->name(). You can retrieve the registered DCOP client -by calling \p kapp->dcopClient(). +equal to \p tdeApp->name(). You can retrieve the registered DCOP client +by calling \p tdeApp->dcopClient(). \section sending_data Sending Data to a Remote Application: @@ -208,7 +208,7 @@ bool BarObject::process(const QCString &fun, const QByteArray &data, TQString result = self->doIt(i); DCOPClientTransaction *myTransaction; - myTransaction = kapp->dcopClient()->beginTransaction(); + myTransaction = tdeApp->dcopClient()->beginTransaction(); // start processing... // Calls slotProcessingDone when finished. @@ -227,7 +227,7 @@ slotProcessingDone(DCOPClientTransaction *myTransaction, const TQString &result) QByteArray replyData; QDataStream reply(replyData, IO_WriteOnly); reply << result; - kapp->dcopClient()->endTransaction( myTransaction, replyType, replyData ); + tdeApp->dcopClient()->endTransaction( myTransaction, replyType, replyData ); } \endcode @@ -548,7 +548,7 @@ that an application that was started via TDELauncher terminates: QByteArray params; QDataStream stream(params, IO_WriteOnly); stream << pid; -kapp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); +tdeApp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); \endcode The task manager of the Trinity panel connects to this signal. It uses an |