diff options
Diffstat (limited to 'dcop/Mainpage.dox')
| -rw-r--r-- | dcop/Mainpage.dox | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/dcop/Mainpage.dox b/dcop/Mainpage.dox index a92fb4e50..423571280 100644 --- a/dcop/Mainpage.dox +++ b/dcop/Mainpage.dox @@ -38,18 +38,18 @@ The manual method is covered first, followed by the automatic IDL method. \section establish Establishing the Connection: -KApplication has gained a method called \p KApplication::dcopClient() +TDEApplication has gained a method called \p TDEApplication::dcopClient() which returns a pointer to a DCOPClient instance. The first time this method is called, the client class will be created. DCOPClients have unique identifiers attached to them which are based on what -KApplication::name() returns. In fact, if there is only a single +TDEApplication::name() returns. In fact, if there is only a single instance of the program running, the appId will be equal to -KApplication::name(). +TDEApplication::name(). To actually enable DCOP communication to begin, you must use \p DCOPClient::attach(). This will attempt to attach to the DCOP server. If no server is found or there is any other type of error, -DCOPClient::attach() will return false. KApplication will catch a dcop +DCOPClient::attach() will return false. TDEApplication will catch a dcop signal and display an appropriate error message box in that case. After connecting with the server via DCOPClient::attach(), you need to @@ -62,7 +62,7 @@ case: appId = client->registerAs(kapp->name()); \endcode -If you never retrieve the DCOPClient pointer from KApplication, the +If you never retrieve the DCOPClient pointer from TDEApplication, the object will not be created and thus there will be no memory overhead. You may also detach from the server by calling DCOPClient::detach(). |