| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
It is the baseline for all subsequent additions.
Change-Id: Ia56da45b8b92dd0224dbeff97976cd06aa25d943
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Coordinates for map items located outside the view port cannot be
converted to and from screen coordinates. During tests pan the map so
that the items under tests are inside the view port.
Tests for panning the map and dragging map items were failing because
mapping between coordinates and screen position only works for visible
screen positions. The MouseAreas under test did not have
preventStealing set, which was causing the map to pan slightly prior to
item drag being detected.
Stop gesture detection for a touch point when the mouse is grabbed by a
child item.
Task-number: QTBUG-31797
Change-Id: I42a801d50c194c6fe9629f3b0de606b406ad8b8c
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
[ChangeLog][QtPositioning] New SatelliteInfo example
added. The example displays the signal strength of surrounding satellites.
The example employs a demo mode on those platforms which don't provide
satellite information
Change-Id: I573266c7a4429c0d2f1bcdfeb01af52ad02efba7
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
New markers added in the mapviewer example were being placed at the top
left hand corner of the displayed map, just out of view. The user had
to pan the map to see the newly added marker.
Changed to position new markers at the location touched by the user to
activate the context menu.
Change-Id: If328e04cfd651a75fb91d599bedbd1129e761c7b
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
| |
Fixes using the slider to zoom the map.
Task-number: QTBUG-34237
Change-Id: I78b005030c3d869e63b9391e41d05ff28caa3cf5
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't see a reason for keeping this. First of all, only half of it is
implemented. Second we can have the same behavior with a normal
MouseArea. The only advantage a MapMouseArea has is that mouse events
are only received in the boundaries of the parent map item. However
with a bit of work in the parent map item we can have this behavior as
well for a normal mouse area.
The only thing we are eventually loosing is the geocoordinate property
of the MapMouseEvent. But this can be easily obtained with the
"toCoordinate" function in the Map item.
Change-Id: Icb176ee7d7c2881df714ab3191fa1f7f5c8915e2
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
Not all service providers support arbitrary search offsets. The offset
attribute has been removed, instead service providers can supply a
previous and next search query in the form of a QPlaceSearchRequest.
Change-Id: If68e969b06f909f3fa62718656cbef70d1bf84a6
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
|
|
| |
simplelog.txt was not deployed when running make install from outside
Qt source tree.
Change-Id: I420a85fc5f74fb1bfc1b3f63e1f88cf0b0e2a0f9
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
| |
Change-Id: I9ef400e22d46e60d50eed785a71e656a0f93fa26
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
| |
This was highlighted during the testing of the Qt 5.2.0 package.
Change-Id: Iab1e6f5f1e1a8ceb62fc44658ec12fb131ccad65
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-34910
Change-Id: I90a1748496b55b2e69db5c94fa217f79d43c176f
Reviewed-by: Jim Ehrismann <jehrismann@blackberry.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
The QtLocation examples are still broken when running make install
but the module is not part of the release anyway.
Task-number: QTBUG-34907
Change-Id: Ie3a35daae3df39747a70ed4bce430ec1a73cbe3d
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
| |
Causes undesirable example structure in Qt release package
Task-number: QTBUG-34907
Change-Id: I47e2205aa6faef388792146b36cf6ae6cae863da
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
An incorrect property name was used.
Change-Id: I75c19bc4914abb5401cc02944081a19da78b38b3
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
| |
Change-Id: I2f236d0bda50f92840f908305916a082fb59700c
Reviewed-by: QTBUG-18405
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
The Google API was turned off mid 2012.
Task-number: QTBUG-31706
Change-Id: Ia7a04ed2e0f6e411f6a65765c59892be4a14ddb5
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
| |
They were Nokia specific and do not have any value anymore.
Change-Id: I08507aff295df5ead1fa8b5b770514150a2e608a
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for Nokia's explore functionality in places. This adds the
ProposedSearchResult search result type. The proposed search result has
a QPlaceSearchRequest, which can be submitted to
QPlaceManager::search() to perform the proposed search.
This has the added advantage that any arbitrary search request can be
returned as a search result. To facilitate this further a search
context field has been added to the place search request. This field
can be used by backends to store additional search context. Other
relevant fields should also be filled in. This allows additional search
context to be kept.
The Nokia v2 places implementation has be updated to use the explore
feature and to return ProposedSearchResults as well as place results.
Task-number: QTBUG-24874
Change-Id: Ib20c5a8c8a60e6bf16f38dcd75961a752b8b1b32
Reviewed-by: Alex <alexander.blasche@digia.com>
|
|
|
|
|
|
| |
Change-Id: I0e29b6ed30e18badd29f4bc1c13a1b3b569e253d
Reviewed-by: Jim Ehrismann <jehrismann@blackberry.com>
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
This moves the docs to its proper place and fixes content as well as
broken links.
There are still some warnings left.
Change-Id: Ie83086f4feabab5f3b3d6c92eb6b401a5ff43e29
Reviewed-by: Alex <alexander.blasche@digia.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-31741
Change-Id: I0ee10f459d79607f06d37ae7317c2d54a8d7d56a
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
| |
Change-Id: I5b0cb7d56997ad7b91c073b3e02b31d0368fdcfa
Reviewed-by: Alex <alexander.blasche@digia.com>
|
|
|
|
|
| |
Change-Id: I2020e744c0da9598713186d60ddcbdd2f5336510
Reviewed-by: Alex <ablasche@gmail.com>
|
|
|
|
|
| |
Change-Id: I61ae1bd1a9f68d120d4e11635f306374b1f494d0
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
| |
Change-Id: Ifd6b6040bd00357bf658f5b51215d4208823bab1
Reviewed-by: Tasuku Suzuki <stasuku@gmail.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The QML list interface was changed, so that there is now a read only
constructor and the default properties are removed. This is because the
original interface was very runtime centric, like other parts in QML.
The new interface was changed for the needs of the QML designer and
debugger.
Task-number: QTBUG-9390
Change-Id: I1ed36c275fc7f8767956e55ad9afddcb293a970c
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
|
|
|
|
|
|
|
|
| |
Change copyrights and license headers from Nokia to Digia
Change-Id: Ic1390da64a219642fa1e1482a7677a4c2db15cbc
Reviewed-by: Janne Anttila <janne.anttila@digia.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
|
| |
In particular coordinates were not handled correctly for the dialog
used to edit places.
Change-Id: Ic1d1876c84c0c9eb57104d7a483800b1c3cc7fe8
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the GeoShape, GeoRectangle and GeoCircle QML elements with
value types. A value type is a better fit for shape types. It is very
similar to a rect with some utility functions.
Declare QGeoShape, QGeoRectangle and QGeoCircle as movable types.
Update documentation.
Change-Id: Id6c48e1e841c68f2f0c5c6a9c4a6580a57e2dfb6
Reviewed-by: abcd <amos.choy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the Coordinate QML element with a value type.
A value type is a better fit for a coordinate. It is very similar to
a vector3d except it has an explicit coordinate system and some utility
functions.
Declare QGeoCoordinate as a movable type.
Update documentation.
Change-Id: I758fa9dfd7154a4d60fb791fe553b9fee3164c2c
Reviewed-by: abcd <amos.choy@nokia.com>
|
|
|
|
|
| |
Change-Id: I792b01ca419ed3a55edaac231e2aed23246f0c15
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-Introduce places_list and places_map examples
As long as app id and token parameters have been supplied to
place-list.qml and places-map.qml, those examples are
self-contained runnable scripts.
-Refactor quickstart structure into an introduction of concepts
and then common use cases. Reference snippets from the
above examples, as opposed to a file containing unrelated
unrunnable code snippets.
-Add screenshots showing the results of the snippet code.
Change-Id: I402995708a0040441ea079ba0fcfdee3ae61ac40
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
Change-Id: I4ceac7bb7027b14f67175c66af142b0b6a9f7ad6
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
Reviewed-by: Laszlo Papp <lpapp@kde.org>
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
This allows the example to build without using deprecated API. What's
more, since QUrlQuery does proper encoding on its own, the example
code looks cleaner.
Change-Id: I2b94ac8d4fbf82cb57368a3c10d49691c0cc0fec
Reviewed-by: David Faure <faure@kde.org>
Reviewed-by: Ian Chen <ian.1.chen@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Update doc on the use of gesture area
Task-number: QTBUG-26554
Change-Id: I8b3374a76455ec2f72f91017d3c1e13b63d6e9e2
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was an assumption in the QML models that if the
QGeoServiceProvider::placeManager() returned null, then places was
not supported. This is no longer the case as incorrect parmeters
may result in null being returned.
Previously a warning was output to console. Instead, if possible,
we set the error status of the model, and set the error string
to the one provided by the QGeoServiceProvider. If it is not
possible, such as in the case of the Icon element, a warning is
output to console but only if it is deemed necessary.
Task-number: QTBUG-26566
Change-Id: I584222af9325ddb8575fa8f77909521c49bc850a
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
The CategoryModel enums did not match the those from the search models.
Change-Id: I9088910812d3624c0260b0a9482470537fd4df3a
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
| |
Change-Id: Id3d5a0dd04d399ccb5252c3820f76102144f2802
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-26529
Change-Id: Ia8ab7cab820b0f41ec8ed9e02d51707c7a18541e
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
|
|
|
|
|
|
| |
Change-Id: I6e19e9fc77fd844b7cb597d62728bf41775a52d6
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
| |
Change-Id: Ibea44442d9fb6ff56c2724186f32d90923a9f392
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recommendations search did not work because a search area
was being passed along with a recommenation id.
Modify the example to only pass a recommendation id by itself.
The PlaceSearchModel had to be updated as well so that whenever a
null searchArea was assigned, the search request would send
a default QGeoShape as a search area, as opposed to not being
updated at all.
Change-Id: Ia55b2d74e7ac770412fb35e295ee07178cfaeb46
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The VideoItem element, which demonstrates how to use a MapQuickItem,
uses elements from Qt Multimedia.
Adds qtmultimedia to sync.profile.
Task-number: QTBUG-26468
Change-Id: Ie0b0027d68588e04dbf0d0e0a6f4f86c6229e6e8
Reviewed-by: Laszlo Papp <lpapp@kde.org>
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Cannot rely on opacity anymore since items with
0 opacity now also gets mouse events.
Task-number: QTBUG-26443
Change-Id: Ia0ad221a73df48d04f9edd30f5a05fe49e4d6b01
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
|
|
|
|
|
| |
Change-Id: Ied6d7831fe7e00f87976a02af3b2a311abadf6be
Reviewed-by: Natalia Shubina <natalia.shubina@nokia.com>
|
|
|
|
|
|
|
|
| |
These elements/properties are deprecated use the MapGestureArea and
gesture properties instead.
Change-Id: I755e69f6394dda7a92c33aa1fe37efcfd84aa9ff
Reviewed-by: Ian Chen <ian.1.chen@nokia.com>
|