summaryrefslogtreecommitdiff
path: root/tests/auto/declarative_core/tst_place.qml
diff options
context:
space:
mode:
authorabcd <amos.choy@nokia.com>2011-12-12 14:35:31 +1000
committerQt by Nokia <qt-info@nokia.com>2011-12-13 07:27:32 +0100
commit2bd57c5e9d739d23144750ee454a18c7970920cc (patch)
tree08f5128daaf2e88002704134d77bb060624fc066 /tests/auto/declarative_core/tst_place.qml
parente76fda37242a0d2e6c6177ac560ec11cac7c7c11 (diff)
downloadqtlocation-2bd57c5e9d739d23144750ee454a18c7970920cc.tar.gz
No need to rexecute query on every added/updated/removed place
The model does not need to be rexecuted time everytime a place changes. For a update, we get the place to call getDetails For a removal, we get the model to remove a place. For an added place we don't do anything, we shouldn't be filtering whether it is relevant to the search query or not, nor should the query be re-executed. Change-Id: Ie60c2d229c151459e55e33a4fe2f8eca251e77e6 Reviewed-by: abcd <amos.choy@nokia.com>
Diffstat (limited to 'tests/auto/declarative_core/tst_place.qml')
-rw-r--r--tests/auto/declarative_core/tst_place.qml4
1 files changed, 0 insertions, 4 deletions
diff --git a/tests/auto/declarative_core/tst_place.qml b/tests/auto/declarative_core/tst_place.qml
index fdc77a96..57b38136 100644
--- a/tests/auto/declarative_core/tst_place.qml
+++ b/tests/auto/declarative_core/tst_place.qml
@@ -601,10 +601,6 @@ TestCase {
compare(removePlace.status, Place.Ready);
- verify(removePlace.placeId === "");
-
- removePlace.placeId = savePlace.placeId;
-
removePlace.getDetails();
compare(removePlace.status, Place.Fetching);