Needed as it turns out the QGeoRouteRequest associated with a QGeoRoute
has to be exposed also through the declarative API (so
QDeclarativeGeoRoute must expose an associated
QDeclarativeGeoRouteRequest).
QDeclarativeGeoRouteRequest was, until now, intended to be only a
one-way API (to feed data into the plugin).
Now that it has also to expose data coming from the plugin, including
the associated extraParameters that do would come anymore from
nested MapParameters but from the QGeoRouteRequest itself.
For this reason the type has to be a QML-friently type.

Change-Id: I083e0fe97ad1088f6084665037003e24edb54371
Reviewed-by: Lars Knoll <lars.knoll@qt.io>

Change-Id: I7b92ecd1862866c3f065447d23957993057f7b8c
Reviewed-by: Helio Chissini de Castro <helio@kde.org>
Reviewed-by: Sérgio Martins <sergio.martins@kdab.com>

So that the files can be found by qtcreator.

Change-Id: I00b0cbcd711b413221a4486234aba8b1c5757cb6
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>

Geometries are now cleared if data is invalid, before early return.

Task-number: QTBUG-66758
Change-Id: Ie89248f78b5fd817a33ed5d6ff56b3547d64a50b
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Fix:
WARNING: qtlocation/src/locationlabs/qlocationlabsglobal_p.h does not have the "We mean it." warning

Change-Id: Iae44606739fce82d113dfdd228a44e1911593598
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

qtlocation/src/imports/positioning/qquickgeocoordinateanimation.cpp:278:106: error: cast between incompatible function types from ‘QVariant (*)(const QGeoCoordinate&, const QGeoCoordinate&, qreal)’ {aka ‘QVariant (*)(const QGeoCoordinate&, const QGeoCoordinate&, double)’} to ‘QVariantAnimation::Interpolator’ {aka ‘QVariant (*)(const void*, const void*, double)’} [-Werror=cast-function-type]
         d->interpolator = reinterpret_cast<QVariantAnimation::Interpolator>(&q_coordinateWestInterpolator);

Change-Id: If8728c01782177aeeb0f64a8637093d0c4c4ee2d
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Couldn't reproduce the bug that was the explained cause and based on the bug
comments it hasn't been reproducible in Qt 5.2+ in 2014 either.

Task-number: QTBUG-36560
Change-Id: I198bbba5a3f00bf49a7efbfde30af1696011efd8
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

The test in the headline failed in CI on first runs, but succeeded in repeats
when it is run alone. This was because the previous test
declarative_ui::MouseArea::test_basic_press_release led to a situation where the
mouseClick() does not actually lead to a click event.

QTBUG-66534 was created to track that bug. Skip the part of the test that leads
to the failure for now.

Task-number: QTBUG-66533
Task-number: QTBUG-66534
Task-number: QTBUG-66216
Change-Id: Iadf3844e97603414594aceafcb1f36cf40653073
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

Change-Id: Ie32717a594ad7a82d1c8eee238ce378bcfadc2ac

 Conflicts:
	.qmake.conf

Change-Id: I0786d8c91141c245f337c31ddcdfcb39e4b8ca41

Introduced in 69a42c4a



Change-Id: I3cace297e0494bdb4da5e6d4d1a634877c66f916
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Task-number: QTBUG-66315
Change-Id: I18af392a00303b3b4c515c8f557e9c3fa09657eb
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

This also changes underscore with dashes, so that only dashes have to
be used in enabling a feature in a configure line.

Change-Id: I83d3412382ed2530dcd574a1c4b7bff9f20cfd6a
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Change-Id: I9a9bfd9474ff4b578367cea3d7697173ec287ca9

 Conflicts:
	src/location/declarativemaps/qdeclarativegeomap.cpp
	src/location/maps/qgeomap.cpp
	src/location/maps/qgeomap_p_p.h
	src/location/maps/qgeorouteparserosrmv5.cpp
	src/location/maps/qgeotiledmap.cpp
	src/positioning/positioning.pro

Change-Id: I42f8b176a8f3e824c7fe5b067a958735173f0dbb

These are experimental anyway, and to be used they have to be explicitly
imported or added in a pro file.

Change-Id: I7ab4391db5d3f22d8cd4c1819ca0610b8739ff7f
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Remove a non-existing header, and add the we mean it disclaimer on a
private header missing it.

Change-Id: I47847f0cf86693298fc1e778979ecfa3d1f9cc34
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Change-Id: I9be01a84ed70daaa47e2d13619060d815d6b9f3c
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Currently it is incorrectly using Q_LOCATION_PRIVATE_EXPORT

Change-Id: Ie7e92fa5ca0379c0bf89055f975da6cf958e049e
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Change-Id: I1fd99fb629e18cc9dba5eae0f1373a01560e272a

Change-Id: I30ffbe559af8cf911a3525b578a875b5dab69c51
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>

Change-Id: Ice71d2cf640f88ea2cdfc93b38412006c6b9f29e
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>

Also fix the include guards

Change-Id: I5ae5125d64fd059b9ab62e7671972c1e00758bba
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Map.setZoomLevel currently clamps the user-set value to a valid range.
The current implementation emits zoomLevelChanged every time the
user-set value is different from the current value.
This patch restrict emission to when the actual value has really
changed.

Change-Id: I2096b666d2a5b1849c9022cad028b826cfee2a78
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>

Apparently m_userMinimumZoomLevel is set but not used when setting
the zoom level.
With this patch, the minimumZoomLevelChanged signal is still emitted
when the "implicit" minimumZoomLevel of the map changes (the one
derived from the map size), but only if no user minimum zoom level
is explicitly set.

Task-number: QTBUG-66107
Change-Id: Id7f87cbd237407b255deea90dad80eeadd2d2f0d
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>

Or else it may become a dangling pointer when Plugin {} gets destroyed
before Map {}

Change-Id: I30d4e1887502d0288d56a4208b338b59116009e6
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Change-Id: I7fb4e263d49b12adf260c71ca99ed8476125b3a6
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Needed, for example, to emit an sgNodeChanged or similar upon addition
of a new map object, *after* the pimpl has been properly injected.

Change-Id: I1442e54aad94c465b0b7b17f1ed92f4900ca1d29
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

Change-Id: I376c28b3bcc1116c87481020a0ee2aaa0476f950
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

Task-number: QTBUG-66263
Change-Id: I62d9c99ce80c8968057ee0488dac413c312c1b20
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

mapbox-gl-native @ 8757164ac8f2b033b2b12d4baf075ed18cfeb2b4

Task-number: QTBUG-64632
Change-Id: I00038790fcfbaa3b91aee6c23e46b654b7e71ad1
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>

delete navigationManager when is not needed anymore

Change-Id: I2bff91ef13369a32e86fba375f7f158b95cf520d
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

Change-Id: I615cc136fc8542f731bc305028aff6dd15fa2c6c
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>

In this way QGeoMap::mapObjects doesn't have to return all map objects,
as the user added ones should be covered by m_pendingMapObjects.

Change-Id: I5c850f2fb820629e0c4dd941d13f04cb3684b898
Reviewed-by: BogDan Vatra <bogdan@kdab.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>

Change-Id: I64ff6c1da227ff4da75944612badc646c5cba3c4
Reviewed-by: BogDan Vatra <bogdan@kdab.com>

This prevents a sort of "call super" antipattern, where each specific
createMapObjectImplementation have to call the setImplementation
internally.

Change-Id: I0babe89a3a01728e95209cf832f4debc3d8af158
Reviewed-by: BogDan Vatra <bogdan@kdab.com>