Development/Tutorials/D-Bus/Intermediate D-Bus

< Development‎ | Tutorials‎ | D-Bus
Revision as of 23:50, 10 March 2007 by Bille (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Abstract

The basic techniques explained in Accessing Interfaces are suitable for using D-Bus methods with relatively simple signatures, but the more complex interfaces often found in the wild require additional techniques to address, explained in this article.

Complex Return Types

QtDBus requires additional setup to deal with methods that return more complex return types than single primitives. The return type needs to be declared to the Qt type system so that it can be demarshalled.

Lists

Lists of values returned by D-Bus methods are mapped to QList in QtDBus. The appropriate specialisation of QList should be declared as a type to the Qt type system, for example:

Q_DECLARE_METATYPE(QList<QDBusObjectPath>)

It is essential that the Q_DECLARE_METATYPE macro is used outside any code blocks or methods in source code. The best place to use it is at the top of the file.

The type should also be declared to QtDbus using:

qDBusRegisterMetaType<QList<QDBusObjectPath> >();

Dicts

The DBus Dict type should map to QMap, example to follow..


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal