| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
So that they can be also visualized in list views or details can be
presented.
Change-Id: Ib8bb48e73624d8bb50073312e7834c3c609c561b
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
| |
This to let the user choose when to do it, if automaticRerouting is
disabled.
Change-Id: I53251dc42fc831da623f135ff3f1c372ee3dac66
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
This patch adds these two properties to the Navigator API to let
the user know when the engine detects that the position source gets
off the route and to choose whether or not let the engine automatically
recalculate routes in that case.
Change-Id: I1f3afc8820dee1dd2042aa05fb0b3284108cb581
Reviewed-by: Alex Blasche <alexander.blasche@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>
|
|
|
|
|
|
|
|
|
| |
Add a block of comment to explain implementors how to implement the
API.
Change-Id: Ib5e2aca11c8b3a91a958d1dc45573189e9ff5a81
Reviewed-by: Michael Brasser <michael.brasser@live.com>
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|\
| |
| |
| | |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Change-Id: Icbebfaae93cc5827d80ef09323ec82868789838a
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
|
|
This patch introduces the abovementioned classes to be subclassed in
plugins.
These are currently private, and intended to be only used in QML through
appropriate wrappers.
Change-Id: I4a063031a983e4bd070f503e1458b62e44c6e340
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|