Kai,
Thank you for your message! I tried and it is well recognized when building
but seems to have no effect ( for example qtbluetooth-config.pri file is
not changed ).
I tried the same syntaxe that you gave me with native-win32-bluetooth and
this one works perfectly. I have no idea why ^^.
Regar
Hi,
> Von: Interest Im Auftrag von Simon FEUTRIER
> Betreff: Re: [Interest] BLE : Bonding and ble security
>
> I'm trying to use "winrt_btle_no_pairing" with QT_CONFIG(feature) to change
> this
> default behaviour. But I swear I'm trying for 2 hours and I cannot achieve
> it. I don't see > whe
Hi,
I'm digging into my problem and keep updating the bug report
https://bugreports.qt.io/browse/QTBUG-86095. I was wondering if it is not
related to the fact that the device is not paired (since last release of Qt
devices are not necessarily paired).
I'm trying to use "winrt_btle_no_pairing" with
There is another possibility. Keep vsync but add a frame delay. That is,
if you know your application can finish each frame in less than, say,
5ms, then you delay the start of each frame loop by 1000/Hz - 5
milliseconds. For 60Hz that means sleeping for 11.6ms after rendering
the last frame. The r
Il 19/08/20 17:57, Daljit Singh ha scritto:
Now I think there might be some ways this could be solved:
Just as an extra data point: have you tried driving the Qt Quick render
loop manually, using QQuickRenderControl?
My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software
