#include <dcopclient.h>
Signals | |
| void | applicationRegistered (const QCString &appId) |
| void | applicationRemoved (const QCString &appId) |
| void | attachFailed (const QString &msg) |
| void | blockUserInput (bool block) |
Public Methods | |
| DCOPClient () | |
| virtual | ~DCOPClient () |
| bool | attach () |
| bool | detach () |
| bool | isAttached () const |
| bool | isAttachedToForeignServer () const |
| bool | acceptCalls () const |
| void | setAcceptCalls (bool b) |
| bool | qtBridgeEnabled () |
| void | setQtBridgeEnabled (bool b) |
| QCString | registerAs (const QCString &appId, bool addPID=true) |
| bool | isRegistered () const |
| QCString | appId () const |
| int | socket () const |
| void | suspend () |
| void | resume () |
| bool | isSuspended () const |
| bool | send (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data) |
| bool | send (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QString &data) |
| bool | call (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &replyType, QByteArray &replyData, bool useEventLoop=false) |
| bool | findObject (const QCString &remApp, const QCString &remObj, const QCString &remFun, const QByteArray &data, QCString &foundApp, QCString &foundObj, bool useEventLoop=false) |
| void | emitDCOPSignal (const QCString &object, const QCString &signal, const QByteArray &data) |
| bool | connectDCOPSignal (const QCString &sender, const QCString &senderObj, const QCString &signal, const QCString &receiverObj, const QCString &slot, bool Volatile) |
| bool | connectDCOPSignal (const QCString &sender, const QCString &signal, const QCString &receiverObj, const QCString &slot, bool Volatile) |
| bool | disconnectDCOPSignal (const QCString &sender, const QCString &senderObj, const QCString &signal, const QCString &receiverObj, const QCString &slot) |
| bool | disconnectDCOPSignal (const QCString &sender, const QCString &signal, const QCString &receiverObj, const QCString &slot) |
| virtual bool | process (const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData) |
| DCOPClientTransaction * | beginTransaction () |
| void | endTransaction (DCOPClientTransaction *t, QCString &replyType, QByteArray &replyData) |
| Q_INT32 | transactionId () const |
| bool | isApplicationRegistered (const QCString &remApp) |
| QCStringList | registeredApplications () |
| QCStringList | remoteObjects (const QCString &remApp, bool *ok=0) |
| QCStringList | remoteInterfaces (const QCString &remApp, const QCString &remObj, bool *ok=0) |
| QCStringList | remoteFunctions (const QCString &remApp, const QCString &remObj, bool *ok=0) |
| QCString | senderId () const |
| void | setDefaultObject (const QCString &objId) |
| QCString | defaultObject () const |
| void | setNotifications (bool enabled) |
| void | setDaemonMode (bool daemonMode) |
Static Public Methods | |
| void | setServerAddress (const QCString &addr) |
| QCString | normalizeFunctionSignature (const QCString &fun) |
| DCOPClient * | mainClient () |
| void | setMainClient (DCOPClient *mainClient) |
| QCString | dcopServerFile (const QCString &hostname=0) |
| QCString | dcopServerFileOld (const QCString &hostname=0) |
Protected Slots | |
| void | processSocketData (int socknum) |
This class provides IPC and RPC for KDE applications. Usually you will not have to instantiate one yourself because KApplication contains a method to return a pointer to a DCOPClient object which can be used for your whole application.
Before being able to send or receive any DCOP messages, you will have to attach your client object to the DCOP server, and then register your application with a specific name. See attach() and registerAs() for more information.
Data to be sent should be serialized into a QDataStream which was initialized with the QByteArray that you actually intend to send the data in. An example of how you might do this:
QByteArray data;
QDataStream arg(data, IO_WriteOnly);
arg << QString("This is text I am serializing");
client->send("someApp", "someObject", "someFunction", arg);
Definition at line 67 of file dcopclient.h.
|
|
Constructs a new DCOP client, but does not attach to any server. |
|
|
Cleans up any open connections and dynamic data. |
|
|
Returns whether the client handles incoming calls.
|
|
|
Returns the current app id or a null string if the application hasn't yet been registered.
|
|
|
Indicates that the application You need to call setNotifications() first, to tell the DCOP server that you want to get these events.
|
|
|
Indicates that the formerly registered application You need to call setNotifications() first, to tell the DCOP server that you want to get these events.
|
|
|
Attaches to the DCOP server. If the connection was already attached, the connection will be re-established with the current server address. Naturally, only attached application can use DCOP services. If a QApplication object exists then client registers itself as QApplication::name() + "-" + <pid>. If no QApplication object exists the client registers itself as "anonymous". If you want to register differently, you should use registerAs() instead.
|
|
|
Indicates that the process of establishing DCOP communications failed in some manner. Usually attached to a dialog box or some other visual aid.
|
|
|
Delays the reply of the current function call until endTransaction() is called. This allows a server to queue requests. Note: Should be called from inside process() only!
|
|
|
Indicates that user input shall be blocked or released, depending on the argument. The signal is emitted whenever the client has to wait too long (i.e. more than 1/10 of a second) for an answer to a synchronous call. In that case, it will enter a local event loop to keep the GUI updated until finally an answer arrives. In KDE, the KApplication object connects to this signal to be able to block any user input (i.e. mouse and key events) while we are waiting for an answer. If we did not do this, the application might end up in an illegal state, as a keyboard shortcut or a mouse action might cause another dcop call to be issued.
|
|
||||||||||||||||||||||||||||||||
|
Performs a synchronous send and receive. The parameters are the same as for send, with the exception of another QByteArray being provided for results to be (optionally) returned in. A call blocks the application until the process receives the answer.
If
|
|
||||||||||||||||||||||||
|
|
|
||||||||||||||||||||||||||||
|
Connects to a DCOP signal.
|
|
|
File with information how to reach the dcopserver.
|
|
|
|
|
|
Returns the current default object or an empty string if no object is installed as default object. A default object receives application-wide messages that have not been processed by the DCOPClient itself.
|
|
|
Detaches from the DCOP server.
|
|
||||||||||||||||||||
|
|
|
||||||||||||||||||||||||
|
Disconnects a DCOP signal.
A special case is when both
|
|
||||||||||||||||
|
Emits |
|
||||||||||||||||
|
Sends the delayed reply of a function call.
|
|
||||||||||||||||||||||||||||||||
|
Searches for an object which matches a criteria.
findObject calls
If A findObject blocks the application until the process receives the answer.
If
|
|
|
Checks whether
|
|
|
Returns whether or not the client is attached to the server.
|
|
|
Returns whether the client is attached to a server owned by another user.
|
|
|
Returns whether or not the client is registered at the server.
|
|
|
Returns whether DCOP events are being processed.
|
|
|
Returns the application's main dcop client. The main client can be used by objects that do not have any specific access to a dcop client. In KDE applications, the main client usually is the same as KAppliction::dcopClient().
|
|
|
Normalizes the function signature A normalized signature doesn't contain any unnecessary whitespace anymore. The remaining whitespace consists of single blanks only (0x20). Example for a normalized signature: "someFunction(QString,int)" When using send() or call(), normalization is done automatically for you.
|
|
||||||||||||||||||||
|
Reimplement this function to handle app-wide function calls unassociated w/an object.
Note that If you do not want to reimplement this function for whatever reason, you can also use a default object or a DCOPObjectProxy.
|
|
|
Process data from the socket.
|
|
|
Returns whether the DCOP - Qt bridge is enabled. By default the DCOP - Qt bridge is enabled.
|
|
||||||||||||
|
Registers at the DCOP server. If the application was already registered, the registration will be re-done with the new appId.
Registration is necessary if you want to allow other clients to talk to you. They can do so using your
|
|
|
Retrieves the list of all currently registered applications from dcopserver.
|
|
||||||||||||||||
|
Retrieves the list of functions of the remote object
|
|
||||||||||||||||
|
Retrieves the list of interfaces of the remote object
|
|
||||||||||||
|
Retrieves the list of objects of the remote application
|
|
|
Resumes the processing of DCOP events.
|
|
||||||||||||||||||||
|
This function acts exactly the same as the above, but the data parameter can be specified as a QString for convenience.
|
|
||||||||||||||||||||
|
Sends a data block to the server.
|
|
|
Returns the appId of the last application that talked to us.
|
|
|
Specify whether the client should accept incoming calls. By default clients accept incoming calls, but not when connected to a foreign server.
|
|
|
Tells the dcopserver to treat the client as daemon client, not as regular client. If the number of regular clients drops down to zero, the dcopserver will emit a KDE termination signal after 10 seconds.
|
|
|
Installs object
All app-wide messages that have not been processed by the dcopclient will be send further to
|
|
|
Sets the application's main dcop client. The main client can be used by objects that do not have any specific access to a dcop client. In KDE applications, the main client usually is the same as KAppliction::dcopClient().
|
|
|
Enables / disables the applicationRegistered() / applicationRemoved() signals. Note that a counter is maintained about how often this method was called. If this method is called twice with They are disabled by default.
|
|
|
Specify whether Qt objects of the application should be accessible via DCOP. By default the DCOP - Qt bridge is enabled.
|
|
|
Sets the address of a server to use upon attaching. If no server address is ever specified, attach will try its best to find the server anyway.
|
|
|
Returns the socket fd that is used for communication with the server.
|
|
|
Temporarily suspends processing of DCOP events. This can be usefull if you need to show e.g. a dialog before your application is ready to accept DCOP requests. Normally the dialog would start an event loop and in this event loop DCOP requests will be handled. Be aware that not responding to DCOP requests may cause other programs that want to communicate with your application, to hang.
|
|
|
Test whether the current function call is delayed. Note: Should be called from inside process() only!
|
1.2.18