| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ib9ad4e5b882239beb3b5ea9935912d5d67e5c374
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I66e54f70ff8a1c01cae92eaf28028ab35a5545cf
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iebfdc9d1eaf83951e401c027caaf67fff7cc7e33
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I65cc5a13854a39b554c123f0a9c382602bec54ab
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ifa22f0f0fbe309339952e7a3716a8a4b8542fb11
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I4d7f7b90fc861fd155f93b9a3b64b90fe5b32c89
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I9cd28a4b68e0ed10818a3faacbd3c65323498594
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I46f7b06800b9328e01833ad2ebba80642b92fb6a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I100af0790eefd9b08ced931cf09e068a6b6ff6f1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I93cf05181a1b1123515ee5974c854ecf736e0d9e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iaaf70bf4ded6ba79cdbab5f13a6f170691ea4643
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#pragma once was never allowed for installed headers¹ and syncqt.cpp
will now start to enforce this, so port the existing users in this
module to traditional header guards.
¹ https://lists.qt-project.org/pipermail/development/2022-October/043121.html
Amends 0fbfa7affa2aa22d338135d6f52ef3d3d4145766.
Pick-to: 6.6 6.5 6.2
Change-Id: Id38cd34f97946e7f7d5033f431876ea8e8b06978
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit 301092d8bd269b02fb8c749e38fa464f819835ab)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iddf4327b4ebdcd33a765cb9ba1cfbad6f74107b0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic1b4e3b58538019d2c3e31c851586ebbc73acd68
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie147970e481f5ab1379f980f711ae6745c27b35d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I1231cb5f6ef5edb34b09a6be9050957ababcb70a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I8bc47a10b026b3b313620966e0acfe8c41bc7dde
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I5901744192f4866af43e1949c54950cc8f4f9676
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I7b51aa1a777634ff5551b704e4a4314708709d9b
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I9dc5ecd0e80c6eb0a8d343a1223de059bf1e6924
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I87d09d90f7e2b127d31b1b6ee8bfcb8291f75cbb
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I3c6fe17c78cc9d139523c69d6854507a98033f85
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I184313b91f6208ae85c75018b3ce748e3c9011df
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I0ad6547f30155f3daf5d31559d9edd1d20d766ee
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Id708681c57134ddda050b8e46ba2a37ff68a72fa
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ibb5d5ff82ebee8e79b52d27b4ca98240644f8416
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib8ac9bd2f9573564c98eebbdbd8becfc2a6603de
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I677d7b5550d4d084ee9fa407e8f5857b71c0b53d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Replace Q_NAMESPACE by Q_NAMESPACE_EXPORT()
Change-Id: I626b744ece5ba4f492b6d1c4caaf149c9981bfa8
Reviewed-by: Brett Stottlemyer <bstottle@ford.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 4c2bb16321f7b1ba37cbd3a1326aa29c399a4810)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Id06a40d4aba6a6d1a084c67ec6358f9b9c0fd982
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's undefined behavior according to C++, even if you don't touch
members, and only happened to work until
qtbase/13074a967f18ed348ab744f7ff831965607a6421 which made it stop
"working".
Add an explicit nullptr check before calling deleteLater().
Amends 35dd08098f8a4b422d523792261aefe039358f6a(!).
Fixes: QTBUG-120242
Pick-to: 6.6 6.5 6.2 5.15
Change-Id: I9ce95f8c8f917549ccfd0040f0cd4f483c3a28d0
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
(cherry picked from commit 4ef440b458c526ad24a3e87d480ddb44c76c6438)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ifbaf2f45aa56be5bed995a5ca2a26c86080894d9
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ia355a13725dafa7a13a98eeec571e14d17757526
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I2a6ec8c2ec7ad94d33701b0b496244bb3a3de33c
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
|
|
|
|
|
| |
Change-Id: Ia871c550b23b090813a2d73ea57c572eeac639e5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I0f13759225a9e932019d0983a7150844d0297a0c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QIODevice subclasses are neither copy- nor movable, so they shouldn't
be marked as trivially relocatable, either. I have a QtCore change
lined up that statically asserts that relocatable types are actually
copyable or movable, and this is holding it up.
It's a public class, though, so we need to be mindful of SC and
BC:
For SC, Q_DECLARE_TYPEINFO never really applied. Yes, you can
construct situations where a user statically asserted that this type
was trivially relocatable, but that's SiC Type A: they just need to
remove the assertion.
For BC, Qt no longer has types that change layout based on QTypeInfo
(hello, Q5List), but user code might, but that's their problem. If
existing code used trivial relocatability (memmove instead of move +
destroy), it can continue to do so, no change there. New code will not
have that optimization, but they're equivalent, as long as relocations
happen atomically in one or the other way. Qt doesn't leak which type
of relocation is chosen between functions (by passing a bool parameter
to a function, e.g.); any use of QTypeInfo is contained within the
function that uses it. If users leak it, that's again their problem.
But we should document it, so:
[ChangeLog][QtRemoteObjects][Potentially Source-Incompatible
Changes][QQnxNativeIo/QIOQnxSource] These classes are no longer marked
as Q_RELOCATABLE_TYPE.
Fixes: QTBUG-119870
Change-Id: I08c082a403433dc571b8c6ab337bdc717919c8b9
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
|
|
|
|
| |
Change-Id: I21f143bf94e2d183a1f7fcee53074885fba5c4c5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib9dd426fb5b3a97c79ed3036eac41d73014fd305
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I1744e9eacfd5b3ae94a21d1646f33fd79f7a6436
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I520e4b85e578c73e5597ab410e557c9e4a1240ad
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ia0f476439432d44a249d4455233ea5bfadde8e78
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Expand the test from just looking for the existence of ENUM
and instead check that a sequence starts with ENUM and is
not followed by a letter.
Pick-to: 6.6 6.5
Fixes: QTBUG-117379
Change-Id: Ibf979eff0efee2fd82eac1c5c20a1a8bbc2ef2e6
Reviewed-by: Brett Stottlemyer <bstottle@ford.com>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
|
|
|
|
|
| |
Change-Id: I67bf8f331bdaf84a8884f0a2a7d23ca10d387ccf
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic16ef74183a278df29eaae49ebdc35930ce33059
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ief4234c1774f267dbfac363abb98df9e227a9eef
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When QDoc parses a project, it parses the source code to extract the
user-provided documentation and perform sanity checkings based on the
code itself on it.
When QDoc parses an "\fn" command as part of this process, it tries to
understand, based on its intermediate representation built on the
information extracted from the code-base, which "documentable element"
the "\fn" refers to.
When QDoc performs this "matching" process, it takes into consideration
only a certain amount of information.
For example, no checking is performed over the template declaration of a
callable.
Due to some upcoming documentation, where two callables are
indistinguishable to the current process, as they differ only in their
template declaration, QDoc will start to take into consideration the
template declaration of a callable when matching.
This implies that an "\fn" command should now provide information
parity, with regards to template declaration for callables, with the
code-base so that QDoc can perform the match correctly.
The documentation for `qRegisterRemoteObjectsServer` /
`qRegisterRemoteObjectssClient` are not in sync with the intended target
template declaration.
Hence, add the missing information to the relevant "\fn" commands.
Task-number: QTBUG-118080
Change-Id: Ia70ad3a0ded11818b298b31d8fab64b62efdd0ce
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When QDoc parses a project, it parses the source code to extract the
user-provided documentation and perform sanity checkings based on the
code itself on it.
When QDoc parses an "\fn" command as part of this process, it tries to
understand, based on its intermediate representation built on the
information extracted from the code-base, which "documentable element"
the "\fn" refers to.
When QDoc performs this "matching" process, it takes into consideration
only a certain amount of information.
For example, no checking is performed over the template declaration of a
callable.
Due to some upcoming documentation, where two callables are
indistinguishable to the current process, as they differ only in their
template declaration, QDoc will start to take into consideration the
template declaration of a callable when matching.
This implies that an "\fn" command should now provide information
parity, with regards to template declaration for callables, with the
code-base so that QDoc can perform the match correctly.
The documentation for some of the members of `QRemoteObjectNode` is not in sync
with the intended target template declaration.
Hence, add the missing information to the relevant "\fn" commands.
Task-number: QTBUG-118080
Change-Id: Ie7420f65980b6a83db107812361b88eebb4212a1
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
|
|
|
|
|
| |
Change-Id: I1654870806857a8c335a6c6992a385e175af98bf
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I02e0d18672dc260793d90c3f015ded95af714f76
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|