| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
It is unfinished and untested, with no support from any backend.
This was the last bit of functionality in the labs module, so
remove that entirely, including the QML plugin and the now unused
QParameterizableObject type.
Change-Id: Ic448e643cb345d1da877137a673ab572c836b3fe
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The feature was designed to enable map backends to implement their own
rendering of the map, and map items. It was never really used by any of
the backends we supported, and introduced a lot of complexity to the
code base.
The idea as such has perhaps merit, but for now we focus on the basic
functionality of Qt Location. Support for Qt Location when the Qt
Quick scene graph is not used is not a part of that.
Change-Id: I08e460043a0bd2600bad79b6ce2bb18e40e19eb6
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
| |
Pick-to: 6.2
Change-Id: I788362fbd2720782d5d1a313a44a908718c9d415
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
|
|
|
|
|
|
|
| |
Remove usages of outdated LGPL3 header that references LICENSES.LGPLv3
instead of LICENSES.LGPL3.
Change-Id: Ied647fc10d2bf051cccc8b38d75570b7caef1f28
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
|
|
|
|
|
|
|
|
| |
This is required to remove the ; from the macro with Qt 6.
Task-number: QTBUG-82978
Change-Id: I1aaf36e893b8f947abd0770acd9d3007cffdcb10
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: Ieae01bc4669cdd503f97399c622989795a0ad734
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
| |
Conincidentally the patch fixes a few other minor deprecation warnings
in the same file too.
Change-Id: Iaf6221cd35cca95415b7d5383477b8c2bcfe92b0
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
This singleton is meant to offer tech-preview map-related API.
It starts with a mapObjectsAt invokable, that can be used to probe
MapObjects at a specific coordinate of a map.
Reference implementation for Q*ObjectQSG, based on QGeoShape::contains,
included.
Change-Id: Ief692eb5a43115ca02d4642c82023d1b2e217400
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change exposes the QAbstractNavigator instantiated by
QDeclarativeNavigator. By doing so, it is possible to expose to the user
engine-specific features and data via properties, signals and methods
added to the QAbstractNavigator subclass.
However, while this approach greatly simplifies the exposure of
such features, it also leads to writing non-cross-plugin code.
Change-Id: I03be9b6d0868d940dc0ac80520f3b507bec2953a
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this patch, Navigator becomes able to expose additional running
navigation information such as distance to next maneuver, traveled
distance, and so on.
This information must be made available by the
engines by emitting the related signals and implement the related
methods, in QAbstractNavigator subclasses.
This patch also groups all navigation read-only progress information
into a property group inside Navigator, called directions.
Change-Id: I00baf64bafe88cd21d4fef06dae0e7331a40ff70
Fixes: QTBUG-70238
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|\
| |
| |
| | |
Change-Id: Ibe88e68076fc3a722432c07fe4c0358f0bb032ea
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-70264
Change-Id: I2922b855d08e42bbd771cc959ea9b6e97eed60b9
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|/
|
|
|
|
|
|
|
| |
It is not allowed to include files within Qt namespace.
See 5b99f3a3 in qtbase dev.
Change-Id: Ic86986ebe5d6beafa32c7634ffb1d4631c411bf9
Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@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: I03294a3ee43097ce535ef7c2805ee33a99e7dd25
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
| |
A new QML type, Navigator, is introduced in Qt.labs.location
Its intended purpose is to be a front-end for the
functionalities offered by NavigationManagerEngines.
Change-Id: Ic93bed0bfaaf32453e759b12a348fa6ef1ae2c93
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
The labs feature will still be controlled by location-labs-plugin
config option. They will simply come from the QtLocation module, and
be exposed to QML via the additional qml plugin in
imports/locationlabs.
Change-Id: I133d625708e78ba5d8121a95e45142aae5ec274b
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: I95b21a8df6e1de600b31ce2fbea55d0a31b31c7f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: Ic8b2ae65f461b55c3f655af66865c4e8bbf50d14
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: I3ce8956ed77d4307521cb6b5e9b53fb4cc5fed7c
Reviewed-by: Michael Brasser <michael.brasser@live.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also adds addMapObject/removeMapObject to MapObjectView
With this patch, MapObjectView becomes the intended way to
programmatically populate a map with map objects. Objects can still
be declared inside a Map{} element, but to programmatically add them
it is necessary to add them to a MapObjectView that is added to the
map.
MapObjectView has then 3 ways to populate the map: via nested map
objects, via a model, and via programmatically added map objects.
All these 3 ways can be used simultaneously.
Change-Id: Ic7712355fa5e5787a0b83d9547693e288cba1960
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
|
| |
Change-Id: I3680550ae22ef4b143f2e545f672905737a41df2
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
Introducing the new labs qml plugin, Qt.labs.location, and
associated qt module.
The intended use is to introduce and validate new QML API
before they can be moved into QtLocation.
Change-Id: If70d1dcedaf708be96e918dc5e25578df93db370
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|