diff options
| author |  Dirk Hohndel <dirk@hohndel.org> | 2016-03-02 09:02:00 -0800 |
|---|---|---|
| committer | Dirk Hohndel <dirk@hohndel.org> | 2016-03-02 09:02:00 -0800 |
| commit | 605d08557396d9e1524c3d2aedf0817b4ac32ce1 (patch) | |
| tree | edd33c80fd38e3151112b7e0cf2f12c922325225 /qt-mobile/qml/DiveDetailsEdit.qml | |
| parent | cd713d421b0fdb7d28b3c19ad0e2d989e62d5ff2 (diff) | |
| download | subsurface-605d08557396d9e1524c3d2aedf0817b4ac32ce1.tar.gz | |
QML UI: resolve confusion about dive list model ordering
Oops, I forgot to take the sort model on top of the model into account.
Now everything should stay consistent - ListView order when accessed from
QML, but internal order when accessing the underlying array.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'qt-mobile/qml/DiveDetailsEdit.qml')
| -rw-r--r-- | qt-mobile/qml/DiveDetailsEdit.qml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/qt-mobile/qml/DiveDetailsEdit.qml b/qt-mobile/qml/DiveDetailsEdit.qml index 38dd5dad9..cd8417e8f 100644 --- a/qt-mobile/qml/DiveDetailsEdit.qml +++ b/qt-mobile/qml/DiveDetailsEdit.qml @@ -38,7 +38,8 @@ Item { // apply the changes to the dive detail view - since the edit could have changed the order // first make sure that we are looking at the correct dive - our model allows us to look // up the index based on the unique dive_id - diveDetailsListView.currentIndex = diveModel.getIdxForId(dive_id) + var newIdx = diveModel.getIdxForId(dive_id) + diveDetailsListView.currentIndex = newIdx diveDetailsListView.currentItem.modelData.date = detailsEdit.dateText diveDetailsListView.currentItem.modelData.location = detailsEdit.locationText diveDetailsListView.currentItem.modelData.duration = detailsEdit.durationText @@ -52,7 +53,7 @@ Item { diveDetailsPage.state = "view" Qt.inputMethod.hide() // now make sure we directly show the saved dive (this may be a new dive, or it may have moved) - showDiveIndex(manager.getIndex(dive_id)) + showDiveIndex(newIdx) } height: editArea.height |