mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-02-19 22:16:15 +00:00
Code Issues Projects Releases Packages Wiki Activity

QML UI: resolve confusion about dive list model ordering

Browse source 
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>
This commit is contained in:
Dirk Hohndel 2016-03-02 09:02:00 -08:00
parent cd713d421b
commit 605d085573
2 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
qt-mobile/qml/DiveDetailsEdit.qml
View file

@ -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