[Development] Bluetooth and NFC vs Reference Platforms

[Kate Alhola]

Manual page says that it returns all local devices QBluetoothHostInfo .
In bluez it uses listAdapters to query list of local bluetooth Adapters.
To get list of remote devices you should use GetProperties to certain
localAdapter and then property named Devices.

Kate



On Tue, Oct 1, 2013 at 1:42 PM, Michael Zanetti
<michael.zanetti at canonical.com> wrote:
> On Tuesday 01 October 2013 12:25:37 Kate Alhola wrote:
>> On Tue, Oct 1, 2013 at 11:23 AM, Michael Zanetti <
>>
>> michael.zanetti at canonical.com> wrote:
>> > On Monday 30 September 2013 13:09:53 Thiago Macieira wrote:
>> > > On segunda-feira, 30 de setembro de 2013 19:39:53, Knoll Lars wrote:
>> > > > >As far as I know from my colleague, it misses some necessary API --
>> > > > >at
>> > > > >least the connection state changes notification and device
>> >
>> > disappearing
>> >
>> > > > >notification.
>> > > > >We could prepare some patches during the next week or two, though
>> > > > >QtBluetooth probably needs few more revisions and API
>> >
>> > changes/fixes...but
>> >
>> > > > >we can't do too much in case of API freeze, you know...
>> > > >
>> > > > A missing feature is for me not enough reason to delay the release of
>> > > > a
>> > > > module. There's always more features we could add to a module. It's
>> >
>> > also
>> >
>> > > > important to get something out and into the hands of people.
>> > > >
>> > > > Feature freeze doesn't imply a full API freeze. We have the alpha/beta
>> > > > period exactly for finding issues and fixing them. A missing signal is
>> > > > something we can fix if required.
>> > >
>> > > Right.
>> > >
>> > > However, if there are major defects in the API, they need to be voiced
>> >
>> > now.
>> >
>> > > Like Lars said before, this API isn't new, so people have had the time
>> > > to
>> > > look at it.
>> > >
>> > > If there are major problems, I expect that they are already known.
>> > > Therefore, post them.
>> >
>> > After having worked quite a bit with the Bluetooth API I wouldn't say it
>> > has
>> > major defects any more.
>>
>> How about getting list of Bound ( and known) Devices from
>> QBluetoothLocalDevice ( or from somewhere else) ?
>> Normal use case is that you use device discovery only when you are pairing
>> new device. After that
>> you only ask locally that is there device already paired and directly
>> connect to that one.
>>
>> I did not found any other practical way to do this that implement it using
>> Dbus for "normal" Linux
>> and JNI to Android.
>
> Shouldn't QBluetoothLocalDevice::allDevices() give that information?
>
> Br,
> Michael
>
>>
>> Kate
>>
>> > Br,
>> > Michael
>> > _______________________________________________
>> > Development mailing list
>> > Development at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/development
>