Porting dcop calls which return a DCOPRef

[David Faure]

On Wednesday 21 June 2006 23:49, Thiago Macieira wrote:
> David Faure wrote:
> >Anyway I just realized that in most cases, the DCOPRef being returned is
> > for an object created in process ... so there is little point in
> > returning the service name again. If I ask konqueror-123 to create a
> > window, the service of the window's dbus object will obviously be part
> > of konqueror-123 too. So I could just s/DCOPRef/QString/ and document
> > that this is a dbus object path. Does this make sense?
> >(see kdebase/konqueror/KonquerorIface.h for an example)
> 
> True. This is exactly the reason why D-BUS has a native type 
> called "Object Path" that you can send and receive over the bus. Prior 
> to "Pattern Buffer" (the new marshalling system), you were not able to 
> place calls directly using "object path" values.
> 
> Now, all you have to do is send a value of type QDBusObjectPath.

Sounds good. However dbuscpp2xml doesn't like that, and skips all such methods.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).