Thanks for bluez_inc, it's so much easier to work with than bluez / dbus :)
A lot of the bluez_inc callbacks just give you an Adapter * or a Device *, but in a system that manages more than one adapter / device, it's hard to know which one is which. So, I need to end up writing some globally-accessible thread-safe data structure that I can pass these pointers to in exchange for some of my application context.
Then it would be trivial to load up the bluez_inc objects with a pointer to my application context, and retrieve it in the various bluez_inc callbacks.
Thanks for
bluez_inc
, it's so much easier to work with than bluez / dbus :)A lot of the
bluez_inc
callbacks just give you anAdapter *
or aDevice *
, but in a system that manages more than one adapter / device, it's hard to know which one is which. So, I need to end up writing some globally-accessible thread-safe data structure that I can pass these pointers to in exchange for some of my application context.If there were functions like
and
Then it would be trivial to load up the
bluez_inc
objects with a pointer to my application context, and retrieve it in the variousbluez_inc
callbacks.