| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I4369e71bbef0c218b35ef3449c5a1615fbf2cb4d
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
| |
Change-Id: I0ada3ad1bbb27f3947497adf4bfeb1469f4a6256
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
|
|
|
|
|
|
| |
Change-Id: I823bd3ebbd74096fc7319147dc7d4ca6ef10e414
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
No incubation cancellation required when an object is removed: the DM
takes care of that.
Handle also the case of itemCreated called during synchronous object
creation, that fires the callback in the middle of the ->object
call.
Task-number: QTBUG-71264
Change-Id: I058a101c754f22f4b6fbcbd7f6f7ded36f3c129b
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
| |
This workaround is currently needed until QTBUG-72930 gets fixed in
qtdeclarative.
Change-Id: Id75fa2048dd6e012c99f61cdc07cfedbe8c6bf83
Fixes: QTBUG-61509
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
This case was not a problem when the only incubation mode was
Asynchronous, because the test for m_map was done in createdItem.
Now that Synchronous is supported too, this check has to be done earlier
or else instantiated items will never be added to the map.
Change-Id: Ifaa033fb0b64cabe74df395fcb387d162cd02b80
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
| |
When "uturn" comes from OSRM, Qt returns UTurnLeft since Right Hand
Traffic is in use in most countries.
This commit allows qml to set traffic side to return correct u-turn
direction.
Task-number: QTBUG-72462
Change-Id: Ifaa002b063159b4e4ee563d007721ba7a4a587a4
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ifd3514a958d0df4320b253c26e3da3a632088be8
|
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently unable to resolve QPointers to pointers
Change-Id: I04b3b7698ea083f83bc2713530656ca8b3f3ac28
Fixes: QTBUG-69512
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In this case, only border geometry was marked dirty, producing a
misplaced polygon.
Fixes: QTBUG-70886
Change-Id: Ied39e523a584976871a655e436daf8c2700458b6
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Order of touch events are not sorted on some platform. When touch point
1 and
2 are swapped, map is rotated 180 degrees in a moment
Change-Id: I9c308b805a6ca54519f26a9ff19217de7f947c17
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
GCC 4.8 doesn't like using QPointer in signal connections.
Change-Id: I9504efb259712a65427ef1366ca562882085404e
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cb19e1f7e3cc2cfee3b8fcbdfa5cd151826dadac fixed a bogus comparison in
an if statement.
However, the correct condition is actually a bug, and should be removed
altogether. The previously incorrect condition was always testing
to false so the problem wasn't triggered.
Task-number: QTBUG-72180
Change-Id: Ia00b55596173474e8c0fe3b0c374490620c6917f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch introduces a new macro, QT_LOCATION_DEBUG, that, when
fed via qmake command line, changes the scope of some members,
adds some extra members and some extra data dumping into these
members.
In this way external code can inspect the state of the renderer
in order to debug it.
The patch also moves a few classes into separate files, as well
as privately exporting them.
Change-Id: I32a042863f78dcd10f94b0b7fe8b90f3fc486891
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
CategoryModel was missing an update call in the ::componentComplete
callback, as well as reacting on the name changed signal of the plugin.
An update call was also missing in the setPlugin method.
This patch makes it react on the attached signal instead, and
adds missing update calls.
Fixes: QTBUG-70254
Change-Id: I1a8de0137b4fe4af7c5ffc848799061147febba2
Reviewed-by: Michael Brasser <michael.brasser@live.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
A dangerous local reference with the same name of a member variable
caused the latter not to be evaluated and the former not to be set.
Change-Id: Iaadcc3bce36f56ed8eeb77374687cf33632abd2f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The incubating indices bookkeeping was wrong.
This patch removes the bookkeeping and relies on the delegate
model doing the right thing when a row is gone but the
delegate still incubating.
Fixes: QTBUG-71264
Change-Id: Ibf5e525aa7ac79faf2fa149b52def05893d0bcc0
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch fixes rendering artifacts with polylines appearing
when rendering large polylines and/or at high zoom levels.
Two problems caused the artifacts:
1.A too close near plane when calculating the projectable region in
QGeoProjectionWebMercator, which presumably introduced numerical
errors when then using such a region to clip data to be projected
using a projection transformation based on the same frustum.
2.Projected polylines too large for qTriangulatingStroker, that would
then introduce artifacts at screen.
To solve 1., as a temporary solution, the distance of the near plane has
been increased to a value that seems safe for zoom levels < 19.
This while a better formula that scales further is being researched.
To solve 2., screen-space line clipping has been brought back from 5.8,
and added on top of mercator-space clipping. This, in theory, should
also increase the performance, allowing qTriangulatingStroker to process
less data.
Task-number: QTBUG-71607
Change-Id: Id774419dde819931e2fdd78b02081695a91302ef
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We can now pass parameters to qdoc commands - use them to automate
the version bumps for documented QML imports.
Also, improve the structure and language on QML module pages.
Change-Id: Id56d36a9bc550ab9a1aea1af6ff8da83e5e1feb9
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Ic49ab959a028adc9edd60018351386d51b2a9bca
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Removing a local variable never used.
Change-Id: Id2517d0f326b16b4b4ad26e53e4115a33f44c7c2
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds support for setting up Mapbox China API base URL + China
government-approved styles.
Change-Id: I66d9e15f336804466285e0996b0e326ef288be44
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So plugins can use it, also stand alone ones, and no ugly
"import ../" anymore.
Change-Id: I4e53815e041e13d495026d60a826a31bccaef2b4
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Bramastyo Harimukti Santoso <bramastyo.harimukti.santoso@pelagicore.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ie8af7ed00a2f97439f6d801b284a49cfcf281ab0
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since Qt 5.12, \code command accepts parameters, and in-line usage
no longer works (and was never documented to work).
Also, use \badcode for qmake snippets to make it appear as plain text.
Task-number: QTBUG-70980
Change-Id: I53cafdc912b4663d03c19b0a0003693330c94f15
Reviewed-by: Martin Smith <martin.smith@qt.io>
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
src/imports/locationlabs/locationlabs.cpp
Change-Id: I362b903966b5087022fd125b511b236323c265ed
|
| |
| |
| |
| |
| | |
Change-Id: I3813b65b18877f5030aea4511ca7cb850874d7c7
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since it is possible that a category has unspecified visibility then
when comparing we still want to match on those. Otherwise it can end up
not finding any matches as a result.
Change-Id: I586bc3c1c91502ff56ea2974ab87a5dddc9d1263
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Convenience method to test if a property is present.
Change-Id: I01c6748e35aadfd89eecebf8b8cc64a278bba87f
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This has been missing until now.
Change-Id: Ida8f7aa0d14e549d1ad1a04a85d096ff5801b71e
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Up till now QGeoManeuvers inside QGeoRouteSegments were generated as
starting maneuvers, that is, related to the beginning of the segment.
But they were documented as being related to the end of the segment.
This patch fixes the documentation.
Change-Id: Ia08ed2bd597b4f63e6b8a7b3518755d895446a92
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Christopher Adams <chris.adams@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
With this geoservice plugins can register Image Providers.
Change-Id: Ie2380d658758d2eba376035b4d0b5d5121cfcde2
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@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>
|
| |
| |
| |
| |
| |
| |
| | |
Previously missing.
Change-Id: Id77a29d6d1fbcb93e265366828ab1203a18e09d7
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds support for route legs, that are the portions
of a route between one waypoint and the next.
QGeoRouteLeg in particular can be seen as an API addition
to QGeoRoute in that it uses and exposes additional methods
added to QGeoRoutePrivate but not used in QGeoRoute.
Currently the request for legs is set to be the same
as the request for the entire route.
Finding the related bounding waypoints has to be done
programmatically using the legIndex property.
Change-Id: If462b1dc6348be16dc96b167db5500f079fe0a64
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch fixes a regression introduced with
367c49e91366aa9b13bc7d64209321168680841e, that doesn't make the Map
emit property changed signals before it is initialized for camera data
properties.
Change-Id: I14ea0a08780d7b2ed79c72f37bc340a1780a0d78
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch makes QDeclarativeGeoMap always refer to QGeoMap
when it comes to setting and getting camera data properties.
The signal emission for each of these properties is also deferred
to the reception of QGeoMap::cameraDataChanged.
This patch also enable plugins to enforce tilt ranges per zoom,
updating the tilt value (as well as any other camera data value)
on their own.
Change-Id: Icc16645ea53fa2b53b33530f802ce390a2479d39
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps Mapbox GL to a new version that fixes the
compilation errors on QNX 7.
Also, enable Mapbox GL Native plugin for QNX.
mapbox-gl-native @ 27b21363e62c105db0b040b4c5a5ef31170ebd30
Task-number: QTBUG-59685
Change-Id: Icc70ab53ba6f76e319feb53858f3614f3edca3e1
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds a setter for the geoShape property, overridden
in the subclasses.
Change-Id: I5fc4d412efee5e95c5650943ea5bf9b72dc40155
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I4c9a27532f96a885d8baa7a790b2b983b2eb3bb3
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds a new signal to QPlaceReply, contentUpdated.
This signal can be emitted in subclasses when the provider is capable
of notifying partial updates of the content.
The typical use case if fetching the data from multiple databases, also
locally instead of over network, and incrementally populating the
results, as opposed to the current way of operating, that is via previous
page / next page, in which case it's the backend who provides the proper
query parameters to obtain the previous or the next page.
This signal is currently handled only for QPlaceSearchReplies in
QDeclarativeSearchResultModel, where such a signal would trigger a
layout update.
Change-Id: I0aaba5aa9249b61c970d3a309d93fab7fc39d667
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now that a delegate model is used internally by MapItemView, this class
is not used any more.
Change-Id: Ic0c35d6797a19549da6bc271b76e3529d812995e
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change allows MapItemView to use a MapItem, MapItemGroup or
MapItemView as delegate.
To achieve this, MapItemView base class also changes from QObject to
MapItemGroup, effectively making MapItemView a MapItemGroup.
Note, though, that MapItemGroup API in Map should be avoided, when
dealing with a MapItemView, and only MapItemView-specific API should be
used.
Tests and example coming after
[ChangeLog][QtLocation] Enabled nesting of MapItemView. This
required a behavioral change, as MapItemView is now a MapItemGroup,
not anymore a plain QObject.
Due to a bug, MapItemView was previously not a Qt Quick Item, making
it possible to create it as a child of any QObject. This has now been
fixed, so if you happen to have a MapItemView in your scene which is
not a child of a Qt Quick Item, you will get an error message.
Task-number: QTBUG-62683
Task-number: QTBUG-62397
Change-Id: Id97e480429e7f952a541fe88df5c01317afeac18
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
This now triggers compile errors on macOS.
Change-Id: I412dd1e3157fd5bf68d0f5fdc125d6eff9d704e7
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will allow moving the visible map area to a subregion
of the viewport, allowing to maintain the desired visible
region visible when overlaying controls on top of the map.
Task-number: QTBUG-68966
Change-Id: Idf4b30f7c1e4062e5e1c0ddc01a31bc856c0bc0c
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Call function templates with explicit type to force call using double
precision arguments even when qreal is defined as float.
Change-Id: Ida5004cdcba9b984a897e2eb7ae15044080d6adc
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|\ \
| |/
| |
| | |
Change-Id: I749522d1f277159d4ee222c59b07044e954c3926
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
labs\qsg\qmappolylineobjectqsg.cpp(103): warning C4138: '*/' found outside of comment
labs\qsg\qmappolygonobjectqsg.cpp(81): warning C4138: '*/' found outside of comment
labs\qsg\qqsgmapobject.cpp(53): warning C4138: '*/' found outside of comment
Change-Id: I5c000dbd40e59af6504b52303bd4ae4a1b782dc9
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This way pages can be changed without resetting the model.
To achieve this, new members into QPlaceSearchRequestPrivate
are introduced, to keep the relationship between a request
for one page, and the previous or the next page.
In this way sparse population of the model becomes possible.
Change-Id: Ic8db0281408f3500ba83f78c7e152ee0b68cd099
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|