[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [Semi-OT] How to get a dbus array of dbus_object_path from a
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2007-02-17 20:27:32
Message-ID: 200702172127.38033.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday 17 February 2007 21:22, Thiago Macieira wrote:
> Iván Forcada Atienza wrote:
> >Is there any way of getting this information using QtDBus???
> >I'm using "QDBusReply< QList<QDBusVariant> > reply =
> > dbus_iface.call("getProperties");" but no success :-(. Also tried
> > QList<QVariant> and QDbusVariant alone with same results.
> >
> >Any hints?
>
> qDBusRegisterMetaType<QVariantList>();
> [...]
> QDBusReply<QVariantList> reply = bus_iface.call("GetProperties");

And, as far as I understand, the Qt4 D-Bus API docs, it should always be 
possible to examine the real call return value, i.e. the QDBusMessage and, by 
examining its contents, find out which type hasn't been declared as a meta 
type yet.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]