| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ie28a256c39234420a0f15748261ead1a11b5f7e2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I000735ff202d4e52a9463acd1600b2670c2c23b7
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie78897658a326778f2c6d38a1d39d3483d0916d1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The dummy plugin appears to have adverse effects on performance on
linux. It causes constant CPU usage in for example KDE's background
daemon, without having any use. The condition should be fixed to only
build when dummy was explicitly enabed.
Pick-to: 6.5 6.2
Fixes: QTBUG-113435
Change-Id: If10750fb08b1537b0108f09f23cff6af10c33c31
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
The function sets the required CMake variables and policies.
Pick-to: 6.5
Task-number: QTBUG-112685
Change-Id: I4dc527e8aff8db880b660bdadc22eb565c88833d
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
| |
Change-Id: Ie4c1f953a91b1b9f407c867cc109784c888d0e5d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I11594ddd3763a942c654d6e12e904bee4671b4ce
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the example to align with the Qt6 Example-Guideline.
https://wiki.qt.io/Qt6/Example-Guideline
Pick-to: 6.5
Task-number: QTBUG-111254
Change-Id: I8d8028ab5351cd801c8ce5126b1ebe5f2d0f4e50
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After changing android target SDK version to 31, some missing values has
to be defined in AndroidManifest.xml.
AndroidManifest.xml template was updated in qtbase in:
56dee3de5e4ac1c4d37a2c5e27361e7ddbdea1a7 commit. In case when example
uses its own AndroidManifest.xml file, it need to be updated separately.
* android:exported="true": because the manifest sets an intent-filter,
and it then has to explicitly to avoid the warning [1].
* android:allowBackup="true": this has to be explicitly set, we set it
to the default value here [2].
* android:fullBackupOnly="false": SDK 23+ use this to deteremine to
user auto backup or not, we set it to the default value here [3].
[1] https://developer.android.com/guide/topics/manifest/activity-
element#exported
[2] https://developer.android.com/guide/topics/manifest/application-
element#allowbackup
[3] https://developer.android.com/guide/topics/manifest/application-
element#fullBackupOnly
Pick-to: 6.5 6.2 5.15
Change-Id: Ic38b7bd686ee98a1a821d5c73a9b969f1b23d2a2
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
| |
Change-Id: Id034540d7035811f03f1ac73a2a922e10e77b7b6
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
`dbusPath()` is defined in several places, and it seems to me that it
can be implemented as a private static data member. When resolved, we
can remove these files from the exclusion list.
Pick-to: 6.5
Task-number: QTBUG-109394
Change-Id: I1f4290fb8495ce1f1c941a46240b60c8fed4bbe4
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: I2d3383dbd893ca42b0a3845456b6924425a99207
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If64588e95c5eaf65da299e79d12d98d2838d3cd2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iae18eb5ad7f1fdd82fa0c75143f9b38d6566b92c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic37cf8607a1d5a6fc758c59f93b5b8a4beea08a4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I749fe430ba49e81a62a2017b75babd9dd099cc48
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I984e6223f1b2b8f3f2fda00183f04b33913a3a69
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I3f3ea8ff51ff4ed6a3e0b539b6d7036cceb3b87c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I6a2416da002f6cf0f81a7d23938218857482e59d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was colliding with a similarly named typedef in
`winrtrotationsensor.cpp` and it seems to me that the name should have
been GyrometerReadingHandler in the first place.
This was causing issue for unity build.
Pick-to: 6.5
Task-number: QTBUG-109394
Change-Id: I721740caaf994ccf5514cbdc93371a3443378270
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
| |
Change-Id: I7044dfbd2eed7470ddb15d792b889d3a236a4802
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
| |
Task-number: QTQAINFRA-5244
Change-Id: Icc848cb77693e33f7be40cf9947fc3dc43189f12
Reviewed-by: Jukka Jokiniva <jukka.jokiniva@qt.io>
Reviewed-by: Simo Fält <simo.falt@qt.io>
|
|
|
|
|
| |
Change-Id: Ifb17e262de3cb528c39c3e5004d54ce55f97f053
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I8d137bcf36096416e100b6ee9541cf93c50f57bf
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I9ec87860cd7b222b8f76fcd9d9671ac4d5e0af55
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I8db6f6ef8340c5579288e469d90998cca7c46056
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
| |
This was previously illustrated by the sensor_explorer example, which
is now a manual test.
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: Id5dceb8bdb5833ebb69818146d163200a93a52e0
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
An unintentional omission I believe
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: I7e2a100175143a4770979f8667ca39d697f9466b
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The example is useful as a sensor testing tool, but less necessary
as an example. The primary demonstrative element of the example was
how to iterate the available sensors, which is covered in a
documentation snippet (followup commit).
This commit also renames the pre-existing widget-based sensor_explorer
manual test to avoid name conflicts, as well as removes the qdoc and qmake
support from the now-a-manual-test application.
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: I422f62f852d0a7e40a76f555ec8aa98404164f7a
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The primary purpose of the grue example is to demonstrate how to create
new sensors. However, while a nice implementation, it doesn't achieve
this purpose particularly well, and is all in all an overly complex
construct given the straightforward purpose (for instance causing build
and deployment challenges).
Instead it should be replaced with a tutorial-like step-by-step guide
on how to add new sensors. The item to track this: QTBUG-111251
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: If353fd019483ad3d608f16d90820c09e676f1df1
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The example doesn't add much demonstration value in comparison to
sensorsshowcase example.
The one unique thing it does demonstrate is ambient light sensor.
That sensor can be added to the sensorsshowcase too; but OTOH it is in
some sense just 'a' sensor among the sensors, and there is probably no
need to use all of them in the examples.
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: I5d0ba59d969b532689e23388cbdda42884838fca
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Maze (QML) example is a nice game implementation, but doesn't add
much demonstration value in comparison to sensorsshowcase example.
The one unique thing it does demonstrate is tilt sensor. Tiltsensor can
be added to the sensorsshowcase too; but OTOH tilt is in some sense
just 'a' sensor among the sensors, and there is probably no need to use
all of them in the examples.
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: I2fd997750b05b3962428955a2929e149af6b72bd
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The example is a simple QML accelerometer example, originally
introduced as a tutorial for creating Android QML applications, and
more importantly superseded by the somewhat recent sensorsshowcase
example.
Task-number: QTBUG-110939
Pick-to: 6.5
Change-Id: I70b37fcf8e876dd6dba102612ca1421f65802d9a
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
| |
Change-Id: I24da0399a275557e64a506612e48e5efdfd8fdb2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I00f692a5efb89be2dd0b615b6c48bbe3fc29cd10
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason for warning was that the qTypedWrapper stored a
QScopedPointer<QSensorReadingPrivate>, which in reality held a more
derived TestSensor2ReadingPrivate. The base class QSensorReadingPrivate
doesn't have a virtual destructor, and ASAN issues a warning when this
more derived type is destroyed via a base class pointer.
Fixes: QTBUG-105173
Pick-to: 6.5
Change-Id: I0740bd804faa44ace65191b948ae1b5eb44b79c0
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
| |
Change-Id: I192b467f031bab8b52339fd2e9f943ba618109d9
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iac33124056c2c10afcadd231f972fea28a3d2389
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
| |
Pick-to: 6.5
Change-Id: I9b85ac5054601f5207cbb525ce7c92c67e54ab06
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-106533
Change-Id: I1fa3e75b5be433184c9259935ffb843f21676e48
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
|
|
|
|
|
| |
Change-Id: Ieabf01eaca1f42aa97002d2c5d93c7cb48a7428a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ia655daf986a7a9e8fb02e1b6c14c557997d600a8
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I18ce5b7cc047c726c49d58cc4ddfcbb36176070e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I73cf3795f2877dc85f291bf1f8c17b559477d8cc
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I4c4fd025448d64eaa7144d97157890630e2fc4ca
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
Option has not effect anymore.
Pick-to: 6.5
Change-Id: Ie2b3482910da85789437008e8a8b1e596d6f4288
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
| |
Change-Id: Iff0ecf909003fbeb53962940586bcad9c2fad0a9
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ifdbecb23aa40020f863280dd8558ffe27e0d39c2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ibc5216b832491653dc0eb79a6161f4e4acf83877
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
|
|
|
|
|
| |
Change-Id: Ifc85d72ac13ca95f6f9d01da59c91f5e61b56f06
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|