| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
So that it can be used to improve the route calculation based on
traffic information or other time-based information (ferries etc.)
Change-Id: I8bdc81046484cc4f0ebfaffbdf6f034c555d7781
Fixes: QTBUG-70503
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
| |
|
|
|
| |
Change-Id: Ie7493cbb33e656c270ef522fa26460461215e145
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| |
|
|
|
|
|
|
| |
Fix warning:
declarativemaps\qdeclarativegeoroutemodel_p.h(270): Warning: Class QDeclarativeGeoWaypoint implements the interface QQmlParserStatus but does not list it in Q_INTERFACES. qobject_cast to QQmlParserStatus will not work!
Change-Id: I3e9d8e6a68a5bb644a9d6ded8982daffaf985c53
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both RouteQuery and Waypoint are currently intended to be a one-way
interface to push data into a route request.
With the upcoming navigation support, there is need for these to become
also a way to report to the user updated request info.
This patch fixes the problem by adding two read only qml properties,
a Waypoint.metadata, that can also be used to read all of what is
being set via Map Parameters, and a RouteQuery.extraParameters,
intended to be used in the same way.
Change-Id: I65e484d96d50e89f44271781cb21e58dfe7badf8
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces QGeoCoordinate with Waypoint as mean to specify
waypoints in a RouteQuery.
This patch also adds a new invokable to RouteQuery, waypointObjects,
to return QDeclarativeGeoWaypoints instead of QGeoCooordinates.
NOTE: If, by 5.11, support to perform implicit conversions in method
invocations based on converters registered in the metatype system
will be added, this method could/should be removed, and
QDeclarativeGeoWaypoint objects should be return as QVariants from
the waypoints() getter, as they could be used in place of
QGeoCoordinate when passing them as arguments.
Task-number: QTBUG-64066
Change-Id: I77747f53cdcbabe6430580b60fa59d4afe8c650a
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch works on top of the previous one, and passes the content of
the map parameters as a QMap<QString, QVariantMap>, where the key is the
parameter type and the value is a map<property name, property value> of
all properties of the map parameter except for the property "type".
To achieve this, a new list property, quickChildren, has been added to
RouteQuery, to pick up Map Parameters declared inside the query
Change-Id: I364f5438e8f4cfc42430bfe448d96519c407eb74
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
|
|
|
|
|
|
| |
[ChangeLog][QtLocation][QGeoRouteRequest/RouteQuery] Add
TrafficFeature to the query features.
Change-Id: I50243865da97e302943f43b0eda430e9d8383880
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
QtLocation quick classes and headers are moved out of the import directory.
The location quick classes are now in a subdirectory inside the main qtlocation
module.
This is necessary in order to privately export certain classes, such as
Map Items classes, and create an API to inject these objects into QGeoMap
to let plugins render the Map Items directly
Change-Id: Ia6ba5f07c4eddd3c4c2ce54bf34f1afcd42c2558
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
