Main Page   Modules   Namespace List   Class Hierarchy   Compound List   File List   Namespace Members   Compound Members   Related Pages  

MyDCOPObject Class Reference

#include <testdcop.h>

Inheritance diagram for MyDCOPObject:

DCOPObject List of all members.

Public Slots

QCStringList functions ()

Public Methods

bool process (const QCString &fun, const QByteArray &data, QCString &replyType, QByteArray &replyData)

Detailed Description

$QTDIR/bin/moc testdcop.cpp -o testdcop.moc g++ -o testdcop testdcop.cpp -I$KDEDIR/include -I$QTDIR/include -L$KDEDIR/lib -L$QTDIR/lib -lkdecore -ldl

Definition at line 45 of file testdcop.h.


Member Function Documentation

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.

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.


The documentation for this class was generated from the following file:
Generated on Wed Aug 13 23:30:29 2003 for kdelibs by doxygen1.2.18