Hi, On Mon, May 2, 2016 at 4:02 PM, Vinicius Costa Gomes <vcgomes@xxxxxxxxx> wrote: > This makes the org.bluez.Device1 UUIDs property to be emitted as soon as > possible, so the ServicesResolved property is only emitted after all > D-Bus objects representing attributes are added to the bus. > > The problem happens because the g_idle'r that actually emits the signals > are unique per D-Bus object, so when multiple properties are emitted > their ordering on the bus will be based on the first signal for each > object. > > In this case, the 'UUIDs' property was scheduled earlier in the mainloop > iteration, then GATT related objects, then the ServicesResolved > property, as the UUIDs and ServicesResolved properties belong to the > same object, they would be emitted together. > > With this patch the UUIDs property is emitted as soon as possible, and > the ordering is kept. After thinking a little more about this, I came up with a version that solves this by tweaking the gdbus behaviour. I will send it a in a few moments, please take a look. -- 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
