| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
So that there's no risk to mix failures when creating multiple
managers.
Task-number: QTBUG-72180
Change-Id: I5c3b18ba17094e1480b2376e37b58d47029ca8f4
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
| |
This method was initially introduced to be used in the engines, when
QDeclarativeNavigatorPrivate was passed in place of
QDeclarativeNavigatorData. Right now there is no use for it.
Change-Id: Ic623d8c56c5685831629a906837b748e1f4017b6
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: I43607931ec071fc25af02ebe4762e456c72c7d01
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
| |
Somehow missing in the previous patch.
Fixes: QTBUG-72281
Change-Id: Ic1bc24f0b241013048f5e02ede8332561212ffd0
Reviewed-by: Michael Brasser <michael.brasser@live.com>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|\
| |
| |
| | |
Change-Id: I79898ba40dcce8054a105867ab2a88f1fba72c1f
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Or else there's no reactive way to tell navigator objects when the user
changes this property.
Change-Id: Ief78facf537a50c15611127c5282c2bcfd59f8fd
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|/
|
|
|
| |
Change-Id: I9027afac6143784b14879889ffd4180ad8269cc4
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Each QDeclarativeNavigator will create and manage its own
QAbstractNavigator using the QNavigationManagerEngine, this way
the QNavigationManagerEngine doesn't have to manage the sessions
itself based on a const reference.
Change-Id: Ibe006524969b4f8100e71ea188d951072b846c6c
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This property tells whether the Navigator should control the Map camera
to keep track of position source updates. This property is enabled by
default, and setting it to false is useful in cases where e.g. the user
starts gesturing over the map area.
Task-number: QTBUG-69031
Change-Id: I86157f69890f8cf0eb60d457d0f9c4134e2befb0
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QDeclarativeNavigator::setRoute takes a QDeclarativeGeoRoute.
This type is not COW, and could be destroyed by the user or the route
model.
This patch stores it inside a QPointer.
It also stores the contained QGeoRoute, that is what the navigation
engines are supposed to use to perform navigation, and is COW.
Task-number: QTBUG-68536
Change-Id: I73fb79faeb3ac9efefcbd778ee106d29fbf26658
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
QDeclarativeNavigator should call QNavigatorManager::start() inside
QDeclarativeNavigator::start(), however because we were already updating
m_active in QDeclarativeNavigator::setActive(), the call for
QNavigationManager::start() never happens.
Task-number: QTBUG-68066
Change-Id: I486381fdec7fc77ac977ee46683fabd2465cf799
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|
|
|
|
|
|
|
|
| |
Since QDeclarativeNavigatorPrivate is what gets passed to the engine,
a QParameterizableObject *q becomes necessary in order to extract
and connect the QGeoMapParameters in the engines.
Change-Id: Id4a8a99f2287faab9c7e67e5355e9c90c33eaa8f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
| |
Change-Id: I8dd9a35b05b7015c8f4fc6badfa0b0909c669e62
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>
|