Re: AVRCP: player object path

Hi Marco, Barry,

On Wed, Jul 20, 2016 at 6:44 PM, Marco Trapanese
[off-list ref] wrote:

Il 20/07/2016 16:39, Barry Byford ha scritto:

quoted

This is something I'm currently trying to get my head around.

There appears to be a dbus.INTROSPECTABLE_IFACE interface that has an
Introspect() method.

I've got an example of using it in Python at:
https://github.com/ukBaz/python-bluezero/blob/master/examples/iterate.py
In build_introspection()

You can do something similar on the command line with:
gdbus introspect --system --dest org.bluez --object-path / --recurse

Hope that helps move you forward.

Hi Barry,
I was able to get it in this way:

quoted

QDBusInterface *iface = new QDBusInterface("org.bluez", "/org/bluez/hci0",
"org.freedesktop.DBus.Introspectable", QDBusConnection::systemBus(), this);
QString xml = iface->call("Introspect").arguments().at(0).toString();

and then I extract the attribute "name" from the second "node" tag...

If the issue under discussion here is how to enumerate these objects
you should use ObjectManager to do that, you can check how
tools/bluetooth-player.c uses our gdbus client helpers to discover the
objects, it should be very straight forward if the D-Bus library has
support for ObjectManager built-in otherwise you may need to do it
yourselves.

-- 
Luiz Augusto von Dentz