Hello,
I have recently discovered an interesting pattern, it seems really handy
to me. However, I wanted to ask for opinions if there are potential bad
sides so that I don't use this in more places.
This is easier to explain directly on an example:
Currently, `ScrollBar`'s documentation ment
Thanks for the hint.. Its close. But not quite there.
In Qt5, there were 2 or 3 call back signals for handling authentication, and
one slot to be called when finished.
Those are missing in Qt6, and I don’t see anyway to set the pin for an
authorized connection.
Scott
-Original Message
I don't get any error reports, and it pairs without authorization.
I never get the system box for the pin. This very strange part, is it leaves
the device in a very weird place system wise.
Its lot listed as a "known device" but its paired from a Win 11 POV
Ill play around some more.
Scott
-
> In Qt5, there were 2 or 3 call back signals for handling authentication, and
> one slot to be called when finished.
> Those are missing in Qt6, and I don’t see anyway to set the pin for an
> authorized connection.
True, the support for those seems to have been dropped in Qt6, without
replaceme
Hi Scott,
the general process in Qt 6 is as Juha has described.
You need to call QBluetoothLocalDevice::requestPairing() with the desired
pairing mode, and then handle the QBLD::pairingFinished() signal.
Also QBLD::errorOccurred() might report PairingError in case something goes
wrong.
Last time
