Hi, This updates AddRemoteData method to create and return device object path. With recent change on how new device objects are created it is no longer possible to create device object from string with org.bluez.Adapter interface. When adding OOB data for specified address device object is created if it was not yet existing. Path to object is returned in AddRemoteData to avoid need for extra FindDevice() call on org.bluez.Adapter to get object maching specified address. Question: Should RemoveRemoteData be updated to accept device path instead of address? (and therefore require existing object, this method doesn't remove object or any storage data but only deletes hash/rand kept in kernel). Szymon Janc (1): dbusoob: Create device object and return it when adding OOB data doc/oob-api.txt | 6 +++++- plugins/dbusoob.c | 28 ++++++++++++++++++++++++---- 2 files changed, 29 insertions(+), 5 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
