.TH "DCOPObjectProxy" 3 "28 Jan 2004" "dcop Library" \" -*- nroff -*-
.ad l
.nh
.SH NAME
DCOPObjectProxy \- You must use a proxy if you want to dispatch method calls for object IDs which dont have (yet) a corresponding \fBDCOPObject\fP.  

.PP
.SH SYNOPSIS
.br
.PP
\fC#include <dcopobject.h>\fP
.PP
.SS "Public Member Functions"

.in +1c
.ti -1c
.RI "\fBDCOPObjectProxy\fP ()"
.br
.RI "\fICreates a new proxy. \fP"
.ti -1c
.RI "\fBDCOPObjectProxy\fP (\fBDCOPClient\fP *)"
.br
.RI "\fIObsolete, do not use. \fP"
.ti -1c
.RI "virtual \fB~DCOPObjectProxy\fP ()"
.br
.RI "\fIDestroy the proxy. \fP"
.ti -1c
.RI "virtual bool \fBprocess\fP (const  \fBQCString\fP &obj, const  \fBQCString\fP &fun, const  \fBQByteArray\fP &data, \fBQCString\fP &replyType, \fBQByteArray\fP &replyData)"
.br
.RI "\fIReimplement this method to dispatch method calls. \fP"
.in -1c
.SS "Protected Member Functions"

.in +1c
.ti -1c
.RI "virtual void \fBvirtual_hook\fP (int id, void *data)"
.br
.in -1c
.SS "Friends"

.in +1c
.ti -1c
.RI "class \fBDCOPClient\fP"
.br
.in -1c
.SH "Detailed Description"
.PP 
You must use a proxy if you want to dispatch method calls for object IDs which dont have (yet) a corresponding \fBDCOPObject\fP. 

This is somewhat like virtual object references in CORBA.
.PP
\fBSee also:\fP
.RS 4
\fBDCOPObject\fP 
.PP
\fBDCOPClient\fP 
.RE
.PP
\fBAuthor:\fP
.RS 4
Matthias Ettrich <ettrich@kde.org> 
.RE
.PP

.PP
Definition at line 350 of file dcopobject.h.
.SH "Constructor & Destructor Documentation"
.PP 
.SS "DCOPObjectProxy::DCOPObjectProxy ()"
.PP
Creates a new proxy. Definition at line 250 of file dcopobject.cpp.
.PP
References QPtrList< DCOPObjectProxy >::append().
.SS "DCOPObjectProxy::DCOPObjectProxy (\fBDCOPClient\fP *)"
.PP
Obsolete, do not use. DCOP clients know about object proxies automatically.
.PP
\fBThis class or method is obsolete, it is provided for compatibility only.\fP Definition at line 257 of file dcopobject.cpp.
.PP
References QPtrList< DCOPObjectProxy >::append().
.SS "DCOPObjectProxy::~\fBDCOPObjectProxy\fP ()\fC [virtual]\fP"
.PP
Destroy the proxy. Definition at line 264 of file dcopobject.cpp.
.PP
References QPtrList< DCOPObjectProxy >::removeRef().
.SH "Member Function Documentation"
.PP 
.SS "bool DCOPObjectProxy::process (const \fBQCString\fP & obj, const \fBQCString\fP & fun, const \fBQByteArray\fP & data, \fBQCString\fP & replyType, \fBQByteArray\fP & replyData)\fC [virtual]\fP"
.PP
Reimplement this method to dispatch method calls. This method is called of all proxies if the \fBDCOPClient\fP knows no object with the id obj. If the first proxy returns true, the \fBDCOPClient\fP will no longer call other proxies.
.PP
The object id obj may be empty for app-wide function calls not associated with any object. 
.PP
\fBParameters:\fP
.RS 4
\fIobj\fP The object id, or empty for app-wide function calls not associated with any object. 
.br
\fIfun\fP 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. 
.br
\fIdata\fP the received data 
.br
\fIreplyType\fP write the reply type in this string 
.br
\fIreplyData\fP write the reply data in this array 
.RE
.PP
\fBReturns:\fP
.RS 4
true if successful, false otherwise. The default implementation returns always false. 
.RE
.PP
Definition at line 270 of file dcopobject.cpp.

.SH "Author"
.PP 
Generated automatically by Doxygen for dcop Library from the source code.
