| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Change-Id: I73ad44222b2ecefca4457b5dd1713207dc515223
Reviewed-by: Andrei Golubev <andrei.golubev@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main changes:
- Introduction of new SensorsQuick library with private exports
- The original QML plugin loads this new library and does little else
- Renamed original 'sensors' plugin as 'declarative_sensors' to provide
an idea what it relates to
- Renamed library headers as private "_p.h" and added "We mean it"
- Changed qmlRegister* calls to QML_ELEMENT macros
- Removed files that are generated in Qt6 (qmldir, plugins.qmltypes)
Task-number: QTBUG-92530
Change-Id: I18f849adabcc79ac47e67305f78aefeee82801bc
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit introduces the bare minimum cmake support that should
unblock the CI and allow further verification and development on most
platforms: macOS, Linux, Win, iOS and Android.
Some clarifications:
* The support for sensorfw backend is very preliminary and can
be enabled later if needed (no Qt6 version of the sensorfw).
* The simulator backend is dropped as obsolete / unnecessary.
* Three examples are currently commented out and shall be ported with
a later commit.
Task-number: QTBUG-92502
Change-Id: Id523d43ed3ef177010dc73afc5812ed374cff0dd
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: Ifea53d932e1c5726c57dc31f0c7a40892db3501c
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|\
| |
| |
| | |
Change-Id: If4b8ecc6e59564b5cf82b91c56baef2c8b96511b
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-82253
Change-Id: I38c24b441c3778ee316651ee5f5eaf6f3abf815d
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|\|
| |
| |
| | |
Change-Id: Iba47a90c345bd18c156ae4bddfa6e9931ff98804
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the QQmlListProperties were constructed on stack-allocated
lists, which immediately turned into dangling pointers on return. Also,
none of the sensor ranges was ever deleted.
Keep the sensor ranges in persistent lists in the private object, parent
them to the main QmlSensor object, and add some tests for them.
Fixes: QTBUG-79224
Change-Id: Ie61d0aaeaaaf998c1d1f46f60c81848ae48659d6
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>
|
|\|
| |
| |
| | |
Change-Id: I729fc3aca8aab817b3e98ddaffd979235308d16b
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-78690
Change-Id: If399aff73104144bfb4b5de74e64ed7b54f8f63d
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: I6cf814d560665490574bd35d5ebfce911a46270f
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Modify all the qmlRegisterModule calls to use minor version 15
because minor version zero from 6.0.0 would make tests fail.
This is similar to what was done in qtdeclarative in
c147b20a2c1299b2d659fe7c9472ae3866b6a425.
Change-Id: Ie46e7d5b6d4cd5e0e8c6eea5b3ebbbdd83343656
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ic691e11af371acfb7706ee218665fb5a9f96a9c3
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-76133
Change-Id: Iae28989a509384c3fad0fe5b4222e5cc1068881c
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I989cc21bdbbd56c3b14b934b3256bda3a01a6764
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
|
| |
Task-number: QTBUG-73739
Change-Id: Id3be3f2d116d7c1ef8541ced2b75043129b08ab5
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
| |
The module API is called "QmlSensors", not "SensorGlobal".
Fixes: QTBUG-74571
Change-Id: Ia998082be99517393389ba3a9785150e97d9c15f
Reviewed-by: Andy Shaw <andy.shaw@qt.io>
|
|
|
|
|
|
|
|
| |
No actual metadata has changed, but this update makes it easier to check that
everything is in sync.
Change-Id: Ib8cb8adbbf1288fc8e3d3495e5fc3bdaf89389af
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
| |
After commit be9a56e5e3ced5d0d668fa24e4c65ae928f2e25a in qtbase, this is
not needed anymore. Instead the resource system injects the plugin entry
point with a reference to all resources.
Change-Id: I4e68865d242f35517fbc179db1c578850025d328
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
| |
Change-Id: If3027bc22486bec4b4b02eea85497578c8bb1b1a
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: I17dec1cd2d4934710663e5fa97c926a65fe301e5
|
| |
| |
| |
| |
| |
| |
| | |
No new types were introduced in Qt 5.10.
Change-Id: I0f172fc46c23e296bdb29f39b7d30a616e7beb0b
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I51c0fc424f44ae68c3c1c4cf6377e7701ee5a0dd
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
| |
Change-Id: Ib258bbc787f43e563fff8af8151ceae87471c672
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
| |
The 5.7 registration is not needed and the comment was wrong as 5.9 is
the first API version with truly new QML API.
Change-Id: I87f1dc040df4eda1784420a7a9bf37a520dfd6f5
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
|
|
|
|
|
|
|
| |
This updates the types to Qt 5.9.
Change-Id: Ice1fd7011eb0ce9bf4ec22e366d0eb7f6678bf75
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/plugins/sensors/ios/ios.pro
Change-Id: I8d9ca692713c8ba5d8c243371474b0e61630b05e
|
| |
| |
| |
| |
| |
| |
| | |
'override' keyword can be used directly since Qt 5.7.
Change-Id: Ibf0fc590f7e247a310a833a22ece700ec75199bb
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
| |
| |
| |
| |
| | |
Change-Id: I57123eed34ee4618f1cba643c2ce49c8c621a6cd
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|\|
| |
| |
| | |
Change-Id: Iaeb7c9f62b50d68e0cedb95c523aebcceb9128c0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 709f6370884b110def2e4665df8fa7bbf5fae734 the plugin loader
is strict about requiring the correct interface id, to avoid loading
unrelated plugins in the loader thread (which they may not be prepared
to do).
Change-Id: I84e4d927489f9a14615db399b560af4b352bf045
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
[ChangeLog][General][QHumiditySensor] Added QHumiditySensor sensor API.
Change-Id: I6dcac53d75ec427fd585de082f4e3a5adb2ebde2
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
|/
|
|
|
|
|
| |
Task-number: QTBUG-53635
Change-Id: I089a793de1c7f7b7224aa1bb6772b6e54a44237c
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: I47e4537c8456e7b762da2a792f0584c1a783db56
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
src/sensors/doc/src/compatmap.qdoc
Change-Id: I4049bc3c335a8a9db5c935032207d0bcfba78480
|
| |
| |
| |
| |
| | |
Change-Id: I9606b50810c63e49f6821e5188df54417601d11a
Reviewed-by: Oliver Wolff <oliver.wolff@theqtcompany.com>
|
| |
| |
| |
| |
| | |
Change-Id: If952d7f9a0888a16c87bc75a96105c5eabc24377
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
| |
| |
| |
| |
| | |
Change-Id: I470d742058d69d517249620b98eef136a9c6ca86
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|/
|
|
|
|
|
|
|
|
| |
From Qt 5.7 -> LGPL v2.1 isn't an option anymore, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
Updated license headers to use new LGPL header instead of LGPL21 one
(in those files which will be under LGPL v3)
Change-Id: Id129b1497aa9d61fd16332e3b324f28dcf7bdd5b
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I9f84dd9595d055f424202fbc65de2198b06ee1f3
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
|
|
|
|
|
|
| |
Change-Id: Ie95283344006821ae2e84a3c6b01532cd4cf340f
Reviewed-by: Vyacheslav Koscheev <vok1980@gmail.com>
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
|
|
|
|
|
|
|
|
|
| |
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: I141862df4ed2475c05ebbeb8fe447c4a6e736849
Reviewed-by: Antti Kokko <antti.kokko@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I4b5bd46487a3589171f115aba1ee1a57d0273f35
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
| |
This was ancient code and qmake got much smarter since then. It caused
an incorrect "qmltypes" make target too.
Change-Id: I4dbbd70a80fac71dbf033e1af9fb5f256c7279c0
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
| |
- Renamed LICENSE.LGPL to LICENSE.LGPLv21
- Added LICENSE.LGPLv3 & LICENSE.GPLv2
- Removed LICENSE.GPL
Change-Id: I99c601a398559886c2900f3e04833acfceba8263
Reviewed-by: Antti Kokko <antti.kokko@digia.com>
Reviewed-by: BogDan Vatra <bogdan@kde.org>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@digia.com>
|
|
|
|
|
| |
Change-Id: I6afcbcf691e203491ee563168c19d084c051a449
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
|
|
|
|
|
| |
Change-Id: Ia70486a0c6b813829ffd633f5334945f73d3b628
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a new sensor type for distance. This sensor type supports new hardware sensors
that can measure physical distance from the device, in centimeters. The API is designed
to mimic the Android API for proximity (TYPE_PROXIMITY), so that if a given proximity
sensor only supports a binary measurement (near vs far), then instead of reporting distance
in cm, the QDistanceSensor will return the max range value to represent far, and a lesser
value to represent close. Using this definition should simplify implementation.
The main reason for not implementing this as a new property of QProximitySensor is that
clients of QProximitySensor have made the assumption that they will receive the readingReady
signal if and only if the reading has changed from near to far or vice versa. Adding a
distance property will break that assumption, as distance has a higher degree of precision.
Change-Id: Ia804948c78ff7391fc8b78df975cddcf861326dc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
| |
Change-Id: I4754a36bd6977cc2bc83a3fee58fb5ce6d2c2c84
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|
|
|
|
| |
Change-Id: I8541601c0bfe2b7c80e88b4617e8215b266fb0bd
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|