diff options
Diffstat (limited to 'dist/changes-5.14.2')
-rw-r--r-- | dist/changes-5.14.2 | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/dist/changes-5.14.2 b/dist/changes-5.14.2 new file mode 100644 index 00000000..4b0fa8a8 --- /dev/null +++ b/dist/changes-5.14.2 @@ -0,0 +1,49 @@ +Qt 5.14.2 is a bug-fix release. It maintains both forward and backward +compatibility (source and binary) with Qt 5.14.0 through 5.14.1. + +For more details, refer to the online documentation included in this +distribution. The documentation is also available online: + +https://doc.qt.io/qt-5/index.html + +The Qt version 5.14 series is binary compatible with the 5.13.x series. +Applications compiled for 5.13 will continue to run with 5.14. + +Some of the changes listed in this file include issue tracking numbers +corresponding to tasks in the Qt Bug Tracker: + +https://bugreports.qt.io/ + +Each of these identifiers can be entered in the bug tracker to obtain more +information about a particular change. + +**************************************************************************** +* QtBluetooth * +**************************************************************************** + + - Windows: + * [QTBUG-80770] Fixed service state (DiscoveryRequired) when service + detail discovery fails. + * [QTBUG-81827] Avoid possible lock when calling + QBluetoothServer::hasPendingConnections. + - Android: + * Fixed the missing QLowEnergyService::error() signal emission if the + error was detected on the Java side. This probably cut 50% of all + errors out. + * Fixed runtime exception that happened when calling "stopLeScan" when + device's Bluetooth adapter is turned off. + * [QTBUG-81875] Fixed QBluetoothDeviceDiscoveryAgent with Android API 29. + * Fixed race condition where incoming and outgoing Low Energy requests + could overwrite each others payload. + - Linux: + * [QTBUG-81696] Added support for characteristic Write Without Response + requests when using BlueZ 5.50 or later. + +**************************************************************************** +* QtNFC * +**************************************************************************** + + - Android: + * Fixed case when QNearFieldTarget::waitForRequestCompleted() did not stop + early (caused overly long timeout case) despite QNearFieldTarget::sendCommand() + having failed already. |