| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The operators were added by
8bf0a15bfc124fbb664592d4c3f29973fc23262e. They were required to
enable QML comparison of those value types.
This requirement was removed by the introduction of
QMetaType::registerEqualsComparator() in Qt 5.5.
Change-Id: I3950726c26144420157f12b59b9c15cc1f5ffc40
Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@theqtcompany.com>
Reviewed-by: Michal Klocek <michal.klocek@digia.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The value type wrapper code was completely removed. Instead
QGeoShape & derived classes and QGeoCoordinate use Q_GADGET
to advertise their meta data which in turn allows QtQML
to dynamically discover the types when needed.
This implies that the above C++ classes become larger as the meta
data is permanently added. On the positive side all QML value type
wrapper were removed which reduces the QML plugin size. At the
same time it becomes significantly easier to use those types in
other QML plugins such as the QtLocation one.
Unfortunately this change comes with an unavoidable behavior change
as well. Previously is was possible to set a width and height
on an invalid QML rectangle. In the case of an invalid rect it was
made valid (setting center to 0,0) before setting the height or
width. The QGeoRectangle class explicitly aborts calls to
setHeight() and setWidth() in case of an invalid rect. From
now on the C++ class behavior is used in QML too. This was
the reason for the change to tst_map_routing.qml in this patch.
Incidentally the documentation always referred to the QGeoRectangle
documentation and thus always stated the now new behavior.
Documentation for the value types and the relevant behavior changes
will be re-added in a later commit.
Each Gadget must be registered
using QMetaType::registerComparators<T>() to enable == and !=
operators in QML. Unfortunately QMetaType requires the operator<
which does not make any sense for the value types touched by
this patch. Right now, a warning is printed. Attempts will
be made to remove the operator< requirement in QMetaType.
Otherwise the warning has to be removed before the release
as they are printed very often.
[ChangeLog][QtPositioning][Important Behavior Changes] The QML
rectangle type ignores setting of the height and width if the
rectangle is invalid. Previously the property setter changed
the rectangle center to QGeoCoordinate(0,0) before setting the
height and width of a previously invalid rectangle.
Change-Id: Iab98ede58066ce03b2b4e0ce03ed85ba7ecb1020
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
|
|
|
| |
Change-Id: I5e3ff34d8724fab19408f42984308ca12b4ff521
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
- Renamed LICENSE.LGPL to LICENSE.LGPLv21
- Added LICENSE.LGPLv3 & LICENSE.GPLv2
- Removed LICENSE.GPL
Change-Id: Iedee2507ab1bd46788409a98505d7be510253110
Reviewed-by: Jani Heikkinen <jani.heikkinen@digia.com>
|
|
|
|
|
|
|
|
|
| |
[ChangeLog][QtPositioning][Position] Added magneticVariation and
magneticVariationValid property to the QML Position type
Task-number: QTBUG-39547
Change-Id: I59d0039f2b501701f67404dabef2ab4c62bcb16b
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
changed section2 to section1
changed section3 to section2
...it looks better to have a section1 because the CSS makes them
look more prominent.
Change-Id: I2e8e336dd38199adcffee1f91a16bc2fae885cfe
Task-number: QTBUG-40335
Reviewed-by: Martin Smith <martin.smith@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
Fix g++-warnings:
qdeclarativeposition.cpp:95:6: warning: 'bool {anonymous}::equalOrNaN(float, float)' defined but not used
qdeclarativeposition.cpp:105:6: warning: 'bool {anonymous}::exclusiveNaN(float,float)' defined but not used
Change-Id: I430864ebbf31592fd1a1cfc5e2f52af7cedc708e
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
tests/auto/qgeocameratiles/tst_qgeocameratiles.cpp
Change-Id: I2bf1657c6dd3b73e654e7db8bdadadfb293e2180
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-38770
Change-Id: Id4577bd23858880b6f406f9d82a8e5195c4e3d8c
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@digia.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: Id06713fea9ce90436a3d65a84cdbd70f07cd9397
Reviewed-by: Rainer Keller <rainer.keller@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: I06fe61d44bce186a118978f17fb66d6fc2cdd543
|
| |
| |
| |
| |
| | |
Change-Id: If46057e48040fda7b61b81e735c171daf2cc7d06
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1.) Reduces the amount of translatable strings as console/qmlInfo() output
is not translated.
2.) Unused error messages have been removed
3.) Additional translation hints have been added.
Change-Id: I59ef36bd75ab1f6d4878657212884e1251b8a04e
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Change-Id: Ic841572e3079c0f600c696b477d9f7220d130029
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Jim Ehrismann <jehrismann@blackberry.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|/
|
|
|
|
|
|
|
|
|
| |
5.2 declaration is no longer needed as it is implicitly done by 5.3/5.4.
The 5.4 declaration is just a redeclaration to introduce 5.4. If a
new type is introduced or an existing type changed it can be removed in
favor of the changed type.
Change-Id: I2113751faff062feaa2f7ea5e3ab9f290e90f0c2
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|\
| |
| |
| | |
Change-Id: I1de140f15e028425e888e6ef52d9f2ff11fd9d5b
|
| |
| |
| |
| |
| | |
Change-Id: I8e2a77a5daade3cc12da95ff12d28977af069e8c
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following issues were fixed:
* The documentation was declaring that it was it QtLocation instead of
QtPositioning.
* Remove module prefix from properties.
* Change property type to coordinate.
* Add since tag.
Task-number: QTBUG-36366
Change-Id: I6e3fd81b377f6c9afd188a2695601ab45485d007
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removes all member variables and replaces them with a QGeoPositionInfo.
Uses the same value changed and validity changed logic for all
properties.
Change-Id: Ic0420ce7a26da2db12c3eabcad4beac83ea332fe
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The QML and C++ position types now provide the same functionality.
Position attributes are always set/reset on every position update. This
ensures that old values of speed, accuracy, direction, and vertical
speed are not indefinitely reported in QML. Values are set to NaN and if
appropriate the associated is valid property is set.
[ChangeLog][QtPositioning][Position] Added direction and vertical speed
properities.
Change-Id: Ia02da8a5bc1cd68489eb58180986df512c24aa2f
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
src/plugins/position/geoclue/qgeopositioninfosourcefactory_geoclue.cpp
Change-Id: Iae3f3c00d46c903e2fa6c1dd49876839362f8001
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
return AllPositioningMethods
Also added unit test for preferredPositioningMethods()
Change-Id: I28c1d5ce66987d3799d1d1cc97469112dd055a45
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: I43e7398a35d963081f5d3eb91598308ea00700e6
|
| |
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-34907
Change-Id: Id119523528c7cd2419be638048f4faf7bf0f2cb9
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: Ia0af08e46e39b783ffa0773bbc43a9a5a78c28bc
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previously described behavior was introduced by a platform
which QtPositioning no longer supports. Effectively this is a
behavior change which currently doesn't affect any known backend.
The upcoming Android & BB10 backends support this new behavior.
The described behavior was very inconvenient from a QML developer's
perspective. Deleting a QML PositionSource is rather inconvenient and
difficult to do. The API should make a developer's life easier.
Task-number: QTBUG-33457
Change-Id: I94432c0569b647cd33c27f75ed73ce5322f40d47
Reviewed-by: Anders Gunnarsson <anders.gunnarsson@appello.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This simplifies various position backend implementations
as they don't have to cast 0 to QGeoPositionInfoSource::PositioningMethods
At the same time we synchronize the same QML enum and its value name.
Change-Id: Ic0b258161a6319da238b265ad5d9926349f461f1
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
This became apparent while implementing the BB10 and Android backends.
Change-Id: I54e2c0fce63021b9fad0c544777792aed726608b
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Change-Id: I6331a0cde85dd3c4ba69e4f67db53e67aa696db1
Reviewed-by: Erik Mattsson <erik.mattsson@appello.com>
Reviewed-by: Anders Gunnarsson <anders.gunnarsson@appello.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Existing 5.2 QML APIs automatically become available
under 5.3 import tags too
Change-Id: I5101c63eaaa00a124475bbc7f60fda0eecfde6ec
Reviewed-by: Erik Mattsson <erik.mattsson@appello.com>
Reviewed-by: Anders Gunnarsson <anders.gunnarsson@appello.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/imports/location/qdeclarativegeomap.cpp
src/imports/location/qdeclarativegeoroute.cpp
src/imports/location/qdeclarativegeoroutemodel.cpp
src/imports/location/qdeclarativegeoroutesegment.cpp
src/imports/location/qdeclarativepolygonmapitem.cpp
src/imports/location/qdeclarativepolylinemapitem.cpp
src/imports/positioning/positioning.cpp
Change-Id: Ieaa5f567d2144d0267e7eef5bd75bde7e0079fbe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The declarative position source only updates its position when an update
arrives. The position property is now updated when:
At construction time the position source may have a last known position
available.
When switching position sources, the position is updated to the last
known position of the new source or invalidated in the case that no
position source is selected.
Change-Id: Ib67407f252f2e60d8fd4e32179847f465c1aaf94
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I8170b591317feb866d208fa4c12a96d3ed52fb7a
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The declarative version of the position info source reuses the C++ enums.
Nevertheless the declarative version may add its own enums as well.
Shift the enum values such that C++ and QML version of the API can stay
in sync and at the same time add values independent from each other.
Change-Id: Ic7082a3d34e7a69f6518a3f1268ee319068bf15d
Reviewed-by: Anders Gunnarsson <anders.gunnarsson@appello.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The QML API remains available under 5.0 though.
Change-Id: I037b82e5b12825db610e8458d6c82122ecde4f44
Reviewed-by: Erik Mattsson <erik.mattsson@appello.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-Links and documentation with type version number no longer recommended
because it is a maintainability and consistency issue.
Use <Module name>::<type> to link to a QML type.
Change-Id: I0f5dcb833c32c3845fc48c18fa29a2c89b13f1d0
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-QDoc ignores these and uses the "\qmlmodule QtPositioning 5.0"
to determine the import statement.
-Better to remove now to avoid confusion.
Task-number: QTBUG-32172
Change-Id: Ic72481de40bdc69b874e9e6ac3339968b6ac208a
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Interpolation logic in AnimatableCoordinate has been moved around so
that QGeoCoordinates can be animated directly by QPropertyAnimation.
A new QML type has been added, 'CoordinateAnimation', for animating
coordinates in QML. This type follows
the pattern of 'ColorAnimation' and other specializations of
'PropertyAnimation'.
QDoubleVector2D, QDoubleVector3D and QGeoProjection has been moved to QtPositioning
Testcase for CoordinateAnimation has been added to declarative_ui.
AnimatableCoordinate and QGeoCoordinateInterpolator are redundant
and have been removed.
Change-Id: I0809da566e1800274384f9c5337df65623d1e61a
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|/
|
|
|
|
|
|
|
|
| |
It will create the smallest possible rectangle that contains all of the
coordinates. This is accessible from qml using the locationsingleton.
The plan is to include the ability to fit the view-port of the map
to a georectangle.
Change-Id: I616ac8ef169f697e53a3d9ebcf114f4f2cde8298
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
nmeaSource property of PositionSource is limited to log files. This
change adds possibility of using a TCP socket instead. This is a lot
more useful when testing because it can be used with a simulator.
Change-Id: Ie6fb2b5344aae2702a8cf53d0146780d6ea1e0f9
Reviewed-by: Albin Olsson <albin.olsson@cybercom.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Rename QGeocoding* classes to QGeoCoding*. This emphasizes the QGeo
prefix rather than the geocing word. The QML interfaces continues to use
the Geocoding* as they don't a prefix as such.
2. Rename QProposedSearchResult to QPlaceProposedSearchResult. The class is place
related and should carry the QPlace name prefix
Change-Id: I428c7e6368774a9f199db5c113de11649e4a665c
Reviewed-by: Kurt Pattyn <pattyn.kurt@gmail.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
QtPositioning is not dependent on any gui component and mostly
covers everything around the retrieval of position information.
QtLocation covers place, map and navigation APIs.
Several documentation issues were fixed during the process.
Change-Id: I98e2a53065549a2fc43f93a75b4f65b5bc884c92
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|