| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I5e18a22a0253520a699213248ce31d11e5fe3ca1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If0b38d222615adec186bd3db269202cf40fef86d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If7887ee8388b3d4c689608f59aa476a8d54ec5f1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ia7d297dd2019a7cbc9b5c8030c422581c2ecaa62
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If59d81e57023a7a522056826094ca458ea9d0028
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
qt_examples_build_begin needs the EXTERNAL_BUILD flag
to know that it's safe to build examples as ExternalProjects.
It still won't do it in CI until we enable building
examples as ExternalProjects for prefix builds.
This is preparation for that.
Task-number: QTBUG-90820
Change-Id: Ifaa60c0cf32b679b3258af23596fee76c95d9b94
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 13082b1331bda2bb95b0245e925f8edf4a7a5f3d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-90820
Change-Id: Idcb45133a1580781c5527c6d9fea1ad0b09bb57d
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 79f01a923491d892b58ba163ead66d639bf184df)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Idcf8ae41b5530169b53c33ee82be0510f51a3609
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ibc179c698f3661f1def066064d44d42b46a0b6c1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I14026c68c64535ca20b62c42eee32c57785edec5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic661245b24db10391d48fb09d25e5a225b016402
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-92967
Change-Id: I95a438c1cce4076499f8ed144fc013b66c1651c1
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit 5aabdf7f5615405c95a380a344803af04e68e97f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Location.hasVerticalAccuracy() and Location.getVerticalAccuracyMeters()
methods are available since API Level 26.
We tried to call these methods without the API Level check, which was
leading to runtime exceptions on Java side.
This patch fixes it.
Fixes: QTBUG-99329
Change-Id: Ib43aec8a3891ab7200d28f6665bd7db60c13495e
Reviewed-by: Juha Vuolle <juha.vuolle@insta.fi>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit c452e9b906e20a6ef1594db0a4543f05b7aed1c2)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie32e7f362ed311e3289cd31c286016d4081aa9fe
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I73ed229d0a742587c36217a1a437487d3170fc80
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I2f94f6dc33bf36829809a17690df585d9e46d3e1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iecfdac4dc42a5957a20d9cd61dc96213846c2adf
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I7c2f35701b4c5b0f6ca7ea6468f504bb265887b0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I18bbdc21d230a4e137f774f1f6cf29feb3354ef7
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I24704ab77844ae0ca5795ca09b99095e96a69f6d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib23dfcc4b900b97d305515f1a5ff38d74e6cf548
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I721c1958c2fb87b7a96274090c3bd9f59f8ceef5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
| |
Looks like it's no longer transitively included
Fixes: QTBUG-98780
Change-Id: Ie2b803acfacfbcbe67a05ea6b473dc88ce12c95f
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit ce76cb1be336d6a50898e028973f35d4c35377fa)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
It's not longer transitively included by qobject.
Change-Id: Iaf7b66478ada03fb62c88d43f2148b0bc909c157
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
(cherry picked from commit 625241669ed8e0e4ec2cf3532f32433dc347bf14)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When instantiating a PositionSource component, someone can explicitly
set the active property to true:
PositionSource {
active: true
...
}
This results in a setActive(true) call during the object instantiation.
When we call setActive(), we delegate the actual update of the 'active'
property to the executeStart() or stop() methods, that are called from
the method.
The setActive(true) call was using QTimer::singleShot(0,...) to put
executeStart() on an event loop. The idea behind it was to make sure
that executeStart() is called when the component is initialized and all
the parameters are set.
The normal call stack for such cases would be:
setActive(true); // during component initialization
componentComplete(); // called when component is ready
tryAttach(); // called from componentComplete()
executeStat(); // from the event loop
This was working fine most of the time. In such scenario the position
source is correctly initialized in tryAttach(), so executeStart() is
doing its work as expected, and updating the 'active' property.
But is some cases instantiating the component could take a longer amount
of time, and executeStart() was called before componentComplete().
In such cases we got the following call stack:
setActive(true); // during component initialization
executeStart(); // from the event loop
componentComplete(); // when component is ready
tryAttach(); // from componentComplete()
Here executeStart() does nothing, because no position source is created
by the time it's called. And when the component is actually instantiated,
there is no sign that we need to call executeStart() again. So the
component's 'active' property is still false.
This patch removes the QTimer approach, and introduces explicit checks
for the component state when setActive() is called. If the component
is already initialized, we can call executeStart() explititly, otherwise
we set a flag, and call executeStart() from tryAttach().
Fixes: QTBUG-97705
Change-Id: I51ffd8106edce7610381e668e186d15a763aeac1
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 290310add82e047757c0ef8f53821d8328b2d321)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Unlike other platforms, on macOS/iOS this property does not allow to
tune the update interval. Extend the docs to explicitly mention it.
Change-Id: I938bec1a6c348f3b5c6140a28f84588e49bbaed9
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 54c65f72b378cb13aba7bc146067b97ca5ec4a87)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The pre-existing code was incorrect due to the operation priority.
The result of the comparison was assigned to the variables, so they
were always initialized with 0 or 1 instead of real values.
Also use std::numeric_limits<double>::lowest(), because the altitude
can have a negative value (when we are below sea level).
Fixes: QTBUG-97722
Change-Id: I2d5beddfdf6d7b4fc626d6b09f4923c968016428
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Juha Vuolle <juha.vuolle@insta.fi>
Reviewed-by: Sona Kurazyan <sona.kurazyan@qt.io>
(cherry picked from commit 70b7818e1fc585f8bac43b721f3dd172b7489d07)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I119078797fd00684816d6e62ead76626ffbc7c6f
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ia63af707257e840d1ea583823043d91a9680f933
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I7ea7ecac18474b99f2e692208881b7b9351ffc0b
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I3068b5a0cbce1953c0dca06cafb2e24dcfbf3461
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
|
|
|
|
|
| |
Change-Id: I83ef1188a7ecc71c4a252d56472a6756ab02cfd8
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Removed xmlpatterns from the qmake dependencies as it not part of Qt 6.
Task-number: QTBUG-91534
Change-Id: I99923c34c09cf865c15e97c6bcaf43bc653ac50b
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 7b4b600913aea276e0745e248a0c5e45e4774977)
Reviewed-by: Tamas Martinec <tamas.martinec@symbio.com>
|
|
|
|
|
| |
Change-Id: I779abb837ea5e84b83341dbc59daae3e0cba4323
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I4f653947da59e72455a380684b574c1c73c0e073
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ica20a74e9500857a81b915ee08bc3b33ecfd4cf5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I5d9bbd98c63387407cdbc5e27bc0cc14b602880d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib56aa534130a3759646fe49a48512bad480145c2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If12f4e4131b091588563254e79ac390c81322a7f
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now when QtPositioning is moved to a separate repo, we need to udpate
conanfile.py to point to the right url + fix some naming
Task-number: QTBUG-97187
Change-Id: I49729e410c1e5df7ce219a31b0fd11e6d89b9e60
Reviewed-by: Iikka Eklund <iikka.eklund@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 2d7ccb7ffba9261477a7cc299bcfa501aabba864)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now when QtLocation and QtPositioning are located in different repos,
we can't include headers from clip2tri 3rd party library into QtLocation
code.
This patch refactors and extends the already-existing wrapper to
completely hide all the clip2tri-related classes. As a result, it is
enough to include only the qclipperutils_p.h private header in QtLocation
module.
The code using clip2tri in QtPositioning is also reworked to use the
updatd wrapper.
Task-number: QTBUG-97084
Change-Id: I80beda0cb5789b573865cfea970c64c4c16f0a2e
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 1ba1bf7b67ea9c4a6a3f1217e70896cd694f091f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Also take this opportunity to remove all .pro files, as we do not use
qmake to build Qt.
.pro files are only left in the examples.
Task-number: QTBUG-97187
Change-Id: Ic2174b5351074b1bc56f9b296d984aafa10dd545
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
(cherry picked from commit 9d7c224e731632ea0fb7c9d2160e2e6546c191db)
|
|
|
|
|
| |
Change-Id: I73cdcd751981a1680b86f00f000ba40f253ed158
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie1a122e872191d491e0f78f5314bfe07b987c851
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib4ceae6c313971ddfabcdf74d48d29b16e6df178
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I49da3d03fae2628c4d5b22b95a68d6202c00d3d9
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I34f6f0aa5a7c84ec8173237e97c955cbbbfbc9b0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I41554c7a16c8ed1cf43d963136b2efd15d8bbbd0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ice430459bac3755a3bb606a55bd84b9ed9469d34
Reviewed-by: Akseli Salovaara <akseli.salovaara@qt.io>
|
|
|
|
|
| |
Change-Id: I6bf2b395263f020f04fce630bbbdfa42151320c0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|