MyDCOPObject Class Reference

Inheritance diagram for MyDCOPObject:

QObject DCOPObject QObject DCOPObject List of all members.

Detailed Description

Definition at line 37 of file dcop_deadlock_test.h.


Public Slots

void slotTimeout ()
void slotTimeout ()
void slotTimeout2 ()
void registered (const QCString &appName)
void unregistered (const QCString &appName)
QCStringList functions ()

Public Member Functions

 MyDCOPObject (const QCString &name, const QCString &remoteName)
bool process (const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData)
 MyDCOPObject (const QCString &name)
bool process (const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData)
void function (const QString &arg1, int arg2)

Member Function Documentation

bool MyDCOPObject::process ( const QCString fun,
const QByteArray data,
QCString replyType,
QByteArray replyData 
) [virtual]

Dispatches a message.

Usually you want to use an IDL compiler to automatically generate an implementation for this function.

If this function returns false, then processDynamic() is called.

Note to implementators: remember to call the baseclasses implementation. It handles the functions "functions()" and "interfaces()" which return the lists of supported functions and interfaces, respectively.

Parameters:
fun is the normalized function signature. Such a signature usually looks like foobar(QString,int). The return type, qualifiers like "const" etc. are not part of the signature.
data the received data
replyType write the reply type in this string
replyData write the reply data in this array
Returns:
true if successful, false otherwise. The default implementation returns false for all fun except "functions()" and "interfaces()".
See also:
DCOPClient::normalizeFunctionSignature()

functions()

DCOPClient::process()

Reimplemented from DCOPObject.

Definition at line 39 of file dcop_deadlock_test.cpp.

bool MyDCOPObject::process ( const QCString fun,
const QByteArray data,
QCString replyType,
QByteArray replyData 
) [virtual]

Dispatches a message.

Usually you want to use an IDL compiler to automatically generate an implementation for this function.

If this function returns false, then processDynamic() is called.

Note to implementators: remember to call the baseclasses implementation. It handles the functions "functions()" and "interfaces()" which return the lists of supported functions and interfaces, respectively.

Parameters:
fun is the normalized function signature. Such a signature usually looks like foobar(QString,int). The return type, qualifiers like "const" etc. are not part of the signature.
data the received data
replyType write the reply type in this string
replyData write the reply data in this array
Returns:
true if successful, false otherwise. The default implementation returns false for all fun except "functions()" and "interfaces()".
See also:
DCOPClient::normalizeFunctionSignature()

functions()

DCOPClient::process()

Reimplemented from DCOPObject.

QCStringList MyDCOPObject::functions (  )  [virtual, slot]

Returns the list of functions understood by the object.

It gets reimplemented by the IDL compiler. If you don't use the IDL compiler, consider implementing this function manually if you want your object to be easily scriptable.

Rationale: functions() allows an interpreter to do client-side type-casting properly.

Note to implementators: remember to call the baseclasses implementation.

Returns:
a list of functions
See also:
interfaces()

process()

processDynamic()

DCOPClient::normalizeFunctionSignature()

Reimplemented from DCOPObject.

Definition at line 139 of file testdcop.cpp.


The documentation for this class was generated from the following files:
KDE Home | KDE Accessibility Home | Description of Access Keys