| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I2b9751dcdcee4a5d8d3353bfc2fcc43cd995b584
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
|
|
|
|
|
| |
Change-Id: Ic45f7c8aa819d373e96cf60082fcda95a63f79b8
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|
|
|
|
|
| |
Change-Id: I780c23ae48c548e799c853cd3a5ac1aa77586839
Reviewed-by: Paolo Angelelli <paolo.angelelli@qt.io>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
| |
Change-Id: Ibbd06c3bc6c2c745a8e2fc6ee12a974bb40bf80a
Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
I forgot QtPositioning when I updated the QtLocation QML qmltypes.
Change-Id: I9616fd510b40c1b58bfce839b3651736c572233a
Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
The class implementing the animation has changed but the API offering
is the same.
Change-Id: I950fea89dc67b60123727d4848488f7fc24374cd
Reviewed-by: Harald Meyer <dev@meh.at>
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
|
|
|
|
|
|
| |
Change-Id: I242622fbb6ba5f63b1fa76e2c01d75f978c8e98a
Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
| |
QGeoPositionSource has such a signal which we need to forward to QML.
Without it QML apps have no way to dertermine a timeout based failure
situation.
Task-number: QTBUG-44663
Change-Id: I1f8da6a61851b4a8302c9558dd2b4a9088be3de5
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The GeoShape is compatibile as the class name changes but
the functionality and naming is the same in QML.
The QtLocation changes are additions which become available
and Qt 5.5. is the first official release anyway. Hence
the normal rules about \since do not apply.
Change-Id: I41d8afea955001845ab143535f6653fce715b9d8
Reviewed-by: Michal Klocek <michal.klocek@theqtcompany.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
| |
Change-Id: I5e3ff34d8724fab19408f42984308ca12b4ff521
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.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>
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| |
| | |
Change-Id: Ia0af08e46e39b783ffa0773bbc43a9a5a78c28bc
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|
|
|
|
| |
Change-Id: I8170b591317feb866d208fa4c12a96d3ed52fb7a
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>
|