Hi Tony,
> -Original Message-
> From: Tony Van Eerd [mailto:tvane...@blackberry.com]
> Sent: Tuesday, 1 October 2013 16:31
> To: Kate Alhola; Blasche Alexander
> Cc: development@qt-project.org
> Subject: RE: [Development] Bluetooth and NFC vs Reference Platforms
>
&
Hi Kate,
> -Original Message-
> From: Kate Alhola [mailto:kate.alh...@gmail.com]
> > While you can get the pairing status for an arbitrary address you cannot
> > get a list
> of a connected device. This requires additional API elements but certainly
> does
> not invalidate any API for
On Tue, Oct 1, 2013 at 2:54 PM, Blasche Alexander
wrote:
>
>>From: development-bounces+alexander.blasche=digia@qt-project.org
>>[mailto:development-bounces+alexander.blasche=digia@qt-project.org] On
>>Behalf Of Kate Alhola
>
>>How about getting list of Bound ( and known) Devices from
>>
>From: development-bounces+alexander.blasche=digia@qt-project.org
>[mailto:development-bounces+alexander.blasche=digia@qt-project.org] On
>Behalf Of Kate Alhola
>How about getting list of Bound ( and known) Devices from
>QBluetoothLocalDevice ( or from somewhere else) ?
>Normal use cas
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 P
On Tuesday 01 October 2013 12:25:37 Kate Alhola wrote:
> On Tue, Oct 1, 2013 at 11:23 AM, Michael Zanetti <
>
> michael.zane...@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:
> > > > >
On Tue, Oct 1, 2013 at 11:23 AM, Michael Zanetti <
michael.zane...@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 --
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
> > >notificati
> -Original Message-
> From: development-bounces+alexander.blasche=digia@qt-project.org
> [mailto:development-bounces+alexander.blasche=digia@qt-project.org]
> On Behalf Of Thiago Macieira
> However, if there are major defects in the API, they need to be voiced now.
> Like Lars s
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, th
On 9/30/13 9:26 PM, "Konstantin Ritt" 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 nee
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
On 9/30/13 7:48 PM, "Konstantin Ritt" wrote:
>2013/9/30 Knoll Lars
>
>On 9/30/13 5:38 PM, "Thiago Macieira" wrote:
>>
>>Similarly for Bluetooth, which exists on all platforms. But since I don't
>>know
>>the QtBluetooth API, I don't know whether the API implemented makes sense
>>for
>>the deskto
2013/9/30 Knoll Lars
> On 9/30/13 5:38 PM, "Thiago Macieira" wrote:
> >
> >Similarly for Bluetooth, which exists on all platforms. But since I don't
> >know
> >the QtBluetooth API, I don't know whether the API implemented makes sense
> >for
> >the desktops. Can someone clarify?
>
> Bluetooth mak
On Monday, September 30, 2013, Knoll Lars wrote:
> On 9/30/13 5:38 PM, "Thiago Macieira"
> >
> wrote:
> >Similarly for Bluetooth, which exists on all platforms. But since I don't
> >know
> >the QtBluetooth API, I don't know whether the API implemented makes sense
> >for
> >the desktops. Can someo
On segunda-feira, 30 de setembro de 2013 16:39:42, Knoll Lars wrote:
> On 9/30/13 5:38 PM, "Thiago Macieira" wrote:
> >Qt Project guidelines say that all features that are relevant for the
> >reference platforms must be implemented in the reference platforms.
>
> No. It has to be implemented on a
On 9/30/13 5:38 PM, "Thiago Macieira" wrote:
>Qt Project guidelines say that all features that are relevant for the
>reference platforms must be implemented in the reference platforms.
No. It has to be implemented on all reference platforms if the module is
an essential module. Add-ons where alw
Thiago Macieira kirjoitti 30.9.2013 kello 18.38:
> Qt Project guidelines say that all features that are relevant for the
> reference platforms must be implemented in the reference platforms.
>
> For NFC, I understand that Mac and Windows (desktop) support is not relevant.
> However, on Linux,
Qt Project guidelines say that all features that are relevant for the
reference platforms must be implemented in the reference platforms.
For NFC, I understand that Mac and Windows (desktop) support is not relevant.
However, on Linux, neard has existed for a while, so I say that Linux support
i
19 matches
Mail list logo
