summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update dependencies on '6.6.0' in qt/qtconnectivityv6.6.06.6.0Qt Submodule Update Bot2023-10-031-1/+1
| | | | | Change-Id: I8962c990dd0d6821b0ef6577e3c23b494bcd9a94 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6.0' in qt/qtconnectivityQt Submodule Update Bot2023-10-021-2/+2
| | | | | Change-Id: I6da75a19f8bcedc69a273ee8ad08d1c2272755cb Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6.0' in qt/qtconnectivityQt Submodule Update Bot2023-09-291-2/+2
| | | | | Change-Id: I0df02a420407b3af84de7ca5e2bc1611dbd58a23 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6.0' in qt/qtconnectivityQt Submodule Update Bot2023-09-281-2/+2
| | | | | Change-Id: I40ff08e2ecc02c1964398bfa7e9ac42a5c963d6c Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Doc: Extend list of highlighted Connectivity examplesKai Köhne2023-09-272-2/+7
| | | | | | | | | Task-number: QTBUG-117221 Change-Id: Idc1d7793c02bc1009f5cc43d30e3208b923ab0ee Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 4de43218466329a45cee1b588964ab811f4fedce) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 2390ba95208c262a114058a86db33249fbb18726)
* Update dependencies on '6.6.0' in qt/qtconnectivityQt Submodule Update Bot2023-09-261-2/+2
| | | | | Change-Id: Id15b2789939a6641e34fce0592317fccb497eb35 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6.0' in qt/qtconnectivityv6.6.0-rc1Qt Submodule Update Bot2023-09-211-2/+2
| | | | | Change-Id: Icf0d3487580b2dfff234ed5ff94b999baf1615a3 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6.0' in qt/qtconnectivityQt Submodule Update Bot2023-09-191-2/+2
| | | | | Change-Id: I6093a25b8bb6e983d849645bebd079384c064a87 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Allow to set user information after detection started for non NDEF tagsJan Moeller2023-09-121-3/+5
| | | | | | | | | | | | | | | | Prior to the NDEF implementation one could change the user information after the target detection started. The limitation seems to only effect NDEF tags, so all other tags should still be able to set the information at a later time. This allows to inform the user about the current progress of the process or inform about errors. Fixes: QTBUG-116563 Pick-to: 6.5 Change-Id: If82ea8c2056eb4c425626b06dac98462e3f0070c Reviewed-by: Lars Schmertmann <lars.schmertmann@governikus.de> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> (cherry picked from commit 76e0b4687ced7e3e54a60c674c9432a3161ce834) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityv6.6.0-beta4Qt Submodule Update Bot2023-09-111-2/+2
| | | | | Change-Id: I7681a5c718fb0bf2f783c80b7f7e46140679eb28 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Bluetooth autotests: do _not_ request permissions to use BTTimur Pocheptsov2023-09-053-14/+18
| | | | | | | | | | | | | | | | | | When running in "ci" test environment, only check them. Normally, requesting a permission may trigger a system (such as macOS) to show a popup/alert, requesting a permission to use Bluetooth. But on CI there is nobody to click 'Allow' button. Even worse though, the 'trick' with a nested loop was quite useless there, test was essentially timing out after 15m instead of interrupting the loop after 30 seconds. Now the part requesting permission is conditional with testing QTEST_ENVIRONMENT env. variable (which contains "ci" when running on CI. Task-number: QTBUG-115945 Change-Id: If7ec8e2bd7a7aa9602a31c5a0f00b756e9523012 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> (cherry picked from commit b0344c5cf3fb85ad26a0cb36b86e085ffe80ee5b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-09-041-2/+2
| | | | | Change-Id: I762ab458f16f50161f2f7cd2beabe4eb031d0354 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Doc: Hide attributions for example icons from overviewKai Köhne2023-09-041-0/+3
| | | | | | | | | | | The code is only used in an example. Task-number: QTBUG-116580 Change-Id: I62786f01e2a368e7439c5fff3a83bff1ad2f0baa Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io> Reviewed-by: Topi Reiniö <topi.reinio@qt.io> (cherry picked from commit 8b1c26be6b984d92260d3599ec52de4c6c579dc6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-09-011-2/+2
| | | | | Change-Id: Ia21568a11d2d5e8000e8433492e2ee5a5548ec4e Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Consider protocols that derive NFCNDEFTag in isNdefTag()Jan Moeller2023-08-301-1/+10
| | | | | | | | | | | | | NFCMiFareTag, NFCFeliCaTag, NFCISO15693Tag, NFCISO7816Tag all derive NFCNDEFTag. Therefor, the current implementation of isNdefTag() will return true for all of these, as they satisfy [conformsToProtocol:@protocol(NFCNDEFTag)]. Fixes: QTBUG-116563 Change-Id: I816cb84b2c06f1f9401fccb3867ab78d3ee075b7 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> (cherry picked from commit 7de85709d6828e7ee9dd4fffd683a8d67228311b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-301-2/+2
| | | | | Change-Id: I5ec55021a4c10eb207816d02ded08f1b9845a01b Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-291-2/+2
| | | | | Change-Id: I15f33b29364a8a55d678314369bf7628dd176b16 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-281-2/+2
| | | | | Change-Id: I24b8e012e1a270e7e06b90107146f8c50fad0a7d Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-251-2/+2
| | | | | Change-Id: Ia08170f8ca5e643588ead182175869668822d24d Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-241-2/+2
| | | | | Change-Id: I11c196b79738e171a2ee3613ed28faf81933f5e2 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-231-2/+2
| | | | | Change-Id: I64d0f02a64a750eda6cd06b41568272c00853814 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Bluetooth: remove custom implementations of qbswap(QUuid::Id128Bytes)Ivan Solovev2023-08-232-18/+0
| | | | | | | | | | | | | Starting from qtbase/470b2b8ad9f28eaf24518dfa3f48cc13fcdc421f qbswap() is provided as a hidden friend for this type, so the custom implementations for Windows and Android backends in Qt Bluetooth are no longer required. Fixes: QTBUG-116341 Change-Id: I451de4249a082331f75c1db93ad420cf96d0e3cc Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 98cddeeb4a9e0c8686e505e5e6b9165970ec3060) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Doc: Add example categories for Qt NFC examplesMats Honkamaa2023-08-211-0/+1
| | | | | | | | Task-number: QTBUG-116273 Change-Id: I99dbca4f4f4f933daced7ca2ff5ae9f1eee9d304 Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io> (cherry picked from commit 29117ff85d373c1eedfa42c1f05078098a76baa0) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Fix translation context of QBluetoothUuid::WeightScaleFeatureFriedemann Kleint2023-08-211-1/+1
| | | | | | | | | Amends 439e818f7843b6a117e1bfe755e313022e14aafa. Change-Id: If08fc84a495d493b463cc71de43237b1cc950a5b Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit a6bac31e41b71aeff6272cf8c34f02b237b21184) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: magic_numbers -= 50Marc Mutz2023-08-181-5/+5
| | | | | | | | | | | | | | | | | | | Prevent code readers from having to compare the long lists of magic numbers in the various bluetooth-specific UUID constructors; they're all the same as the ones used in the quint32 ctor, so use C++11 ctor delegation to make all ctors call the quint32 one. This calls into question the need of the quint16 ctor, seeing as the quint32 ctor could just do the former's job with an implicit conversion. But removing it would allow users to pass any integral type to the QBluetoothUuid ctor, which is not the case atm, because the two integral ctors make each other ambiguous unless the arguments match either parameter types exactly. So leave it in. Change-Id: I40ddc47149cbb0526ad6488f32cc7f203e70a6b3 Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 08a0f404f60e5c02dfb3cf7b224feae7e93359b8) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: inherit all ctors from QUuidMarc Mutz2023-08-184-18/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | QBluetoothUuid clearly is-a QUuid, so it should have the same constructors, though it may add its own on top. Three Qt releases (6.3-6.6) of QUuid changes have, however, not been properly reflected in QBluetoothUuid, so fix it once and for all by adding using QUuid::QUuid; to QBluetoothUuid, thereby inheriting all the QUuid ctors (except SMFs) that QBluethoothUuid doesn't supply itself. This fixes or simplifies: - The Id128Bytes ctor, which we don't need to supply at all now. - The QString ctor, which was replaced by a QAnyStringView overload in QUuid a long time ago (6.3). - Anything else that we have missed in the past (GUID, e.g.). The superfluous constructors still have to be retained in the ABI, because QBluetoothUuid is unfortunately exported wholesale. This affects only the QString ctor. The other one was not in 6.5, and we don't provide BC with pre-releases of Qt. Add some variance to the fromString() tests now that we have QAnyStringView instead of just QString. Found in API-review. [ChangeLog][QtBluetooth] QBluetoothUuid now provides all the constructors that QUuid also provides (incl. from GUID and QAnyStringView). Change-Id: I2cb76a9a9cbc47f2fd4e637bdb41233d1ffc6972 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> (cherry picked from commit aff0acdeee12acf6a85f479f160a0d4776f79d7c) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: inline the (quint128, Endian) ctorMarc Mutz2023-08-182-20/+4
| | | | | | | | | | | | | | | | | We can actually write a body that works for both unsigned __int128 as well as the legacy struct quint128, using QUuid::fromBytes(), so do that. This removes the need to keep a complex implementation behind the ABI boundary, and thus allows to remove the function from the ABI so we don't run into even more BiC problems once MSVC starts supporting __int128, possibly with just a newer /std flag which, as per current rules, isn't supposed to change the ABI. Change-Id: I1975cf68bc5f5421bf90f81a691ddf68bfa928dd Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> (cherry picked from commit 0f689ee079aa98b26efe097c8dc6652055f9010b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: inline converting ctor from QUuidMarc Mutz2023-08-172-5/+12
| | | | | | | | | | | | | | | | | It really shouldn't be out-of-line. We should allow the compiler to see it as the no-op that it is. As a drive-by, pre-program the signature to pass by value come Qt 7, fixing a Clazy warning. We could already do it now, but since T and const T& don't overload, we'd have to take out the QT6_NEW_OVERLOAD bazooka, and it's not really worth it. When the code is inline, the compiler can see through the pass-by-reference overhead and avoid allocating the argument on the stack. Change-Id: Ic708bb9b2cacd4df22313b704de557dbda4d28fa Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 6bbf186d135e731e3c7b84a0c3cf9e74c946d32d) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityv6.6.0-beta3Qt Submodule Update Bot2023-08-161-2/+2
| | | | | Change-Id: I6269e3b356344ee945dbcf4f89788999c0f7521f Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* QBluetoothUuid: cut out the streamingOperator() middle-manMarc Mutz2023-08-153-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | The split into an inline friend op<< and an out-of-line streamingOperator() just causes the QDebug object to be copied once more than otherwise necessary. Relegate the streamingOperator() middle-man to QT_REMOVED_SINCE status and make op<< the real thing. We can't make the named function call op<<, because Thiago says there are situations in which the op<<(QDebug, QBluetoothUuid) call in removed_api.cpp, if we were to use it, would get resolved to an exported version of the old op<< in a user library compiled without -fvisibility-hidden, creating a cycle. Fortunately, the implementation is simple enough to make a DRY violation acceptable. Problem exists in 6.5, too, but let's get as many removed_api.cpp tasks done for 6.6, because the QT_NO_INT128 in removed_api.cpp will make a QT_REMOVED_SINCE(6, 7) in this header file that much harder. Change-Id: I10b42cfc1565db8d9a6924cee0af8fb6623c9000 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit a16133c959151892a386204aa54c8115992c1075) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: provide Endian overloads for quint128 functionsMarc Mutz2023-08-153-31/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This mimicks the new APIs of the same name in QUuid. For QBluetoothUuid, this is wonderful news, because the old overloads that lack the Endian parameter are now _always_ referring to the old struct quint128, and are, as usual, defined in removed_api.cpp¹ ¹ with the caveat that QT_NO_INT128 is defined there globally, which may create problems for potential QT_REMOVED_SINCE(6, 7)s. A solution would be to move this stuff out into a compat/old_int128_api.cpp, but let's first get the 6.6 part done. The new overloads are now either `unsigned __int128` (#ifdef QT_SUPPORTS_INT128) or `struct quint128` (otherwise), never both, so we don't need a second TU to do the overloading at the ABI level. This leaves removed_api.cpp with its traditional role of dealing with QT_REMOVED_SINCE (with the caveat mentioned above) and the QT_SUPPORTS_INT128 handling is in qbluetoothuuid.{h,cpp}, where it belongs. This greatly simplifies the #ifdef'ery in all three files and allows to do away with the "normal" vs. "not typical" QT_REMOVED_SINCE(6, 6) section split. Amends 5d90296f312f72ffa6a5322df7b565c3e5521684. As a drive-by, fix missing Q_QDOC handling. Change-Id: I4ead4ee39533967a78c145ef222d9991fdf4cd98 Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit bfa5d5f6581439216ccbff97e1c9af76fc461dc7) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-151-1/+1
| | | | | Change-Id: Ia1807fccabd3dc7c47e03c6c07ca8ca6983f7a12 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-151-2/+2
| | | | | Change-Id: I4249f5ff17695326cced8140d7a6939b58d30630 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* tst_QBluetoothUuid: add tests for (QString) ctorMarc Mutz2023-08-121-0/+6
| | | | | | | | | | | | We already have the string representation QFETCH()ed, so let's use it. This also seems to test op<<, by QCOMPARE() falling back to QDebug::toString(). Change-Id: Ibec66d4b7301e71509497a06b1b65e5cf9d108c2 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> (cherry picked from commit 9122bfcc4d332e95209a954785a700bf33adce59) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: remove default case labels and fix the falloutMarc Mutz2023-08-121-8/+4
| | | | | | | | | | | | | | | Learn to love -Wswitch and avoid default case labels even at the cost of having a few enumerator cases "too many". They help catch mistakes, like, in this case, the missing handling of QBluetoothUuid::CharacteristicType::WeightScaleFeature. [ChangeLog][QtBluethooth][QBluetoothUuid] Fixed missing result of characteristicToString(CharacteristicType::WeightScaleFeature). Change-Id: I04b7cf9ee058ef5a8d202fff01fb347d315562f6 Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 439e818f7843b6a117e1bfe755e313022e14aafa) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: remove unused equals() method declarationMarc Mutz2023-08-121-3/+0
| | | | | | | | | | | This was never used, nor even defined, ever since the declaration was added in 9c59558afc71f36a82a1cab9ca0841119892e26a, so it doesn't need QT_REMOVED_SINCE(). It just was whitespace. Change-Id: I6a56cbe346455818c13cefb66c65887edbfcb0e9 Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit 85e4b9f7c66bf653ec295a52305b5f1224eda3c6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: insulate against potentially-disappearing QUuid(quint128) ctorMarc Mutz2023-08-121-1/+1
| | | | | | | | | | | | | | | | | | | We're considering remove the QUuid(quint12*) ctor in favor of the "named" fromUInt128() ctor, so isolate the code against that by going via the Id128Bytes ctor, which always exists. This particular way of writing the code requires C++20/C99 designated initializer support enabled in the compiler. It just so happens that the only compiler that doesn't support __int128 (MSVC) also is the only compiler that doesn't allow the use of designated initializers in C++17 builds (because MSVC never implemented C99), only in C++20+ ones, so for the moment we're ok. If this becomes a problem, we can rewrite the code. Change-Id: Ic4424ddad1a8a703e00b2ff3d9b45b07bb321fd0 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> (cherry picked from commit 5fcb55cf2bd45408162d20fe5be407ce6494ba5f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: add missing Endian argument to Id128Bytes ctorMarc Mutz2023-08-112-4/+5
| | | | | | | | | | | | | | | | The base class has it, so QBluetoothUuid also has to have it, too, for API symmetry. Adapt the docs to be more like QUuid's for the same function, even though those may still be improved in qtbase (in which case we shouldn't forget to re-sync them here). Found in API-review. Change-Id: If13df1e7551235e2c9f57ba0e8729d7f2a6d494c Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit a2944859ac2a6a13100b5a06c681fb477231e52a) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-081-2/+2
| | | | | Change-Id: Icb155b253ab3ee44e3b0a4a994362e9bfef19c23 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* QBluetoothUuid: keep custom quint128 and related methods when 128-bit ints ↵Ivan Solovev2023-08-034-12/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | are not supported ... to retain SC with prior Qt versions. For QBluetoothUuid::toUInt128() this is done by introducing an extra condition to the method declaration and definition. If the 128-bit ints are not supported, we shouldn't hide the method under QT_BLUETOOTH_REMOVED_SINCE. The QBluetoothUuid(quint128) c-tor is a bit more tricky, because we need to provide a forwarding c-tor to be able to use QUuid(quint128) c-tor. And at the same time, we need to keep BC by keeping the constructor that takes custom struct quint128. This is achieved by having an unconstrained c-tor declaration and two implementations: * an implementation in qbluetoothuuid.cpp is only available when Qt supports 128-bit ints. It just forwards to the QUuid c-tor. * an implementation in removed_api.cpp serves as a backup implementation to keep BC for the case when Qt supports 128-bit ints. And at the same time it serves as a main implementation when 128-bit ints are not supported. Also extend the unit-tests to explicitly check that both APIs are available on all platforms. The test additionally makes sure that QUuid::toUInt128() and QBluetoothUuid::toUInt128() provide the result which is similar to QUuid::toBytes(). This guarantees compatibility between platforms. This commit amends 1e903be81f43da4e31385bb7866bb4d3f07e5eba. Change-Id: I6ba3ff6278e6db11a372b46f001429f4466520a0 Reviewed-by: Marc Mutz <marc.mutz@qt.io> (cherry picked from commit 5d90296f312f72ffa6a5322df7b565c3e5521684) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-08-021-2/+2
| | | | | Change-Id: I3346a77334cce53f84dd745dde6fcea2c2bb9f16 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-07-311-2/+2
| | | | | Change-Id: I266938fa8af183e0e35ebffd14bdc91f0d5fa8d7 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-07-261-2/+2
| | | | | Change-Id: I5ba2cadb9bc2c9745049fb0585b3094837d913fb Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-07-211-2/+2
| | | | | Change-Id: I25f3e00b03ff908e95ff22d03b3c703587bff7fe Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Doc: List of all Qt overviews which are now termed as explanationJaishree Vyas2023-07-191-0/+1
| | | | | | | | | | | | | The autogenerated list of overviews was adding the \group command which included all the groups instead of overviews. The idea here is to categorize the overviews later on once we have the list of all overviews. Task-number: QTBUG-114762 Change-Id: I3cf53886be277abc86b5ec54d399cd6933fbe882 Reviewed-by: Kai Köhne <kai.koehne@qt.io> (cherry picked from commit f7ae4d2aa8bfd37f5cf0a98afbe58328407784b5) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* Update dependencies on '6.6' in qt/qtconnectivityQt Submodule Update Bot2023-07-121-2/+2
| | | | | Change-Id: Idfcf2d1070b1ab36fd5b36b97d426ea6c8a8ca57 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
* Doc: Remove \ingroup all-examples command from the docsJaishree Vyas2023-07-122-2/+0
| | | | | | | | Task-number: QTBUG-115044 Change-Id: I83314f3b7955e1ef9c857bcc96c07f6f90b2f875 Reviewed-by: Topi Reiniö <topi.reinio@qt.io> (cherry picked from commit 9cc12e95730c671eaaa669d131d031fc1453279f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothUuid: fix alignment of the custom quint128 structIvan Solovev2023-07-112-3/+6
| | | | | | | | | | | | | | Updating the struct to contain the Id128Bytes member instead of an array of chars changes the alignment of the struct. Revert the struct to its original state, and update the code in removed_api.cpp to adapt to the changes. This commit partially reverts 1e903be81f43da4e31385bb7866bb4d3f07e5eba Change-Id: I638622ffa5320f8de3f7866109fcc384b557392e Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit b23456ca14ae203df3228c51db2df55cb1f67d70) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothAddress: restore missing move SMFsMarc Mutz2023-07-091-0/+2
| | | | | | | | | | | The user-defined copy SMFs were deleting the move SMFs. Restore them with a strategic =default. Change-Id: I461975ca422cb08c615e910643da2b932c5b45d4 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> (cherry picked from commit a0495c038b8e187f8c48cbee3352b147eb81e462) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
* QBluetoothAddress: inline most functionsMarc Mutz2023-07-093-42/+40
| | | | | | | | | | | | | | | | | | | | This class is supposed to be a _thin_ wrapper around a quint64. It's not extensible anymore, anyway, because inline functions (e.g. the relational operators) access m_address, so we might was well inline all the trivial functions. Do that. Since the class is exported, we need to us QT_INLINE_SINCE. As a drive-by, make all newly-inline functions noexcept. Drop the documentation of the copy SMFs and the destructor. They're trivial, we're not documenting the SMFs of e.g. QUuid, either. Change-Id: I7d5207cb24ea637d5b6eefe0ab8ce54a4b123305 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 7f248fed3d19ca73580d02f5b4ae3d009b90fadf) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-09 15:48:37 +0000