# class DCOPObjectProxy | You must use a proxy if you want to dispatch method calls for object IDs which dont have (yet) a corresponding DCOPObject. More...
Definition | `#include <dcopobject.h>`
List of all Methods
Annotated List
Files
Globals
Hierarchy
Index

#### Public Methods

- DCOPObjectProxy ()
- DCOPObjectProxy ( DCOPClient*)
- virtual ~DCOPObjectProxy ()
- virtual bool process ( const QCString& obj, const QCString& fun, const QByteArray& data, QCString& replyType, QByteArray &replyData )

## Detailed Description

You must use a proxy if you want to dispatch method calls for object IDs which dont have (yet) a corresponding DCOPObject. This is somewhat like virtual object references in CORBA.

DCOPObjectProxy () | ### DCOPObjectProxy

Create a new proxy.

DCOPObjectProxy ( DCOPClient*) | ### DCOPObjectProxy

Obsolete, do not use. DCOP clients know about object proxies automatically.

~DCOPObjectProxy () | ### ~DCOPObjectProxy

[virtual]

Destroy the proxy.

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

[virtual]

Reimplement this method to disptatch method calls.

This method is called of all proxies if the DCOPClient knows no object with the id `obj`. If the first proxy returns `true`, the DCOPClient will no longer call other proxies.

The object id `obj` may be empty for app-wide function calls no associated with any object.

- Author: Matthias Ettrich <ettrich@kde.org>
- Generated: root@sparc.ports.openbsd.org on Wed May 2 09:33:39 2001, using kdoc 2.0a53.