diff options
author | Alex Blasche <alexander.blasche@qt.io> | 2018-10-03 11:05:01 +0300 |
---|---|---|
committer | Alex Blasche <alexander.blasche@qt.io> | 2018-10-04 07:32:23 +0000 |
commit | 8cdcc580a2b38cf7f43bd62de13e11e201647a4a (patch) | |
tree | 96ced490b749dc9578b7950e5f3c20eb320fe2d0 | |
parent | 5ec4a37bd3d3d13e6d5be918ca4c9f9979655af9 (diff) | |
download | qtconnectivity-8cdcc580a2b38cf7f43bd62de13e11e201647a4a.tar.gz |
+ 4d73d1bee26b95a53650a42cb7c425c51b8b7f98 Bump version
+ 5ec4a37bd3d3d13e6d5be918ca4c9f9979655af9 fix use of default constructed QBluetoothSocket
Change-Id: I07bcc1469f14d1998efee4b14b7faaec04b04dd2
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
-rw-r--r-- | dist/changes-5.9.7 | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/dist/changes-5.9.7 b/dist/changes-5.9.7 new file mode 100644 index 00000000..1927c2e0 --- /dev/null +++ b/dist/changes-5.9.7 @@ -0,0 +1,29 @@ +Qt 5.9.7 is a bug-fix release. It maintains both forward and backward +compatibility (source and binary) with Qt 5.9.0 through 5.9.6. + +For more details, refer to the online documentation included in this +distribution. The documentation is also available online: + +http://doc.qt.io/qt-5/index.html + +The Qt version 5.9 series is binary compatible with the 5.8.x series. +Applications compiled for 5.8 will continue to run with 5.9. + +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. + +**************************************************************************** +* Qt 5.9.7 Changes * +**************************************************************************** + +QtBluetooth +----------- + + - Fixed incorrect handling of socketType passed via default constructor vs. the + socketType implied by QBluetoothServiceInfo::socketPotocol(). In some cases + connectToService() was applying the wrong socketType. |