mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Dive pictures: don't repopulate DivePictureModel on deletion
On deletion of a single or multiple pictures, the whole DivePictureModel was repopulated, which was clearly visible in the UI, owing to the reconstructing of all images in the profile plot. To avoid this vexing behavior, implement proper deletion routines in DivePictureModel and ProfileWidget2. Since this needs sensible erase() semantics the QList<PictureEntry> member of DivePictureModel was replaced by a QVector. A QVector should be the default anyway, unless there are very specific reasons to use a QList (which actually is a deque, not a classical linked list). Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
parent
3c0c1801cd
commit
f47f2773fd
4 changed files with 32 additions and 3 deletions
|
@ -149,7 +149,22 @@ void DivePictureModel::removePictures(const QVector<QString> &fileUrls)
|
|||
copy_dive(current_dive, &displayed_dive);
|
||||
mark_divelist_changed(true);
|
||||
|
||||
updateDivePictures();
|
||||
for (int i = 0; i < pictures.size(); ++i) {
|
||||
// Find range [i j) of pictures to remove
|
||||
if (std::find(fileUrls.begin(), fileUrls.end(), pictures[i].filename) == fileUrls.end())
|
||||
continue;
|
||||
int j;
|
||||
for (j = i + 1; j < pictures.size(); ++j) {
|
||||
if (std::find(fileUrls.begin(), fileUrls.end(), pictures[j].filename) == fileUrls.end())
|
||||
break;
|
||||
}
|
||||
|
||||
// Qt's model-interface is surprisingly idiosyncratic: you don't pass [first last), but [first last] ranges.
|
||||
// For example, an empty list would be [0 -1].
|
||||
beginRemoveRows(QModelIndex(), i, j - 1);
|
||||
pictures.erase(pictures.begin() + i, pictures.begin() + j);
|
||||
endRemoveRows();
|
||||
}
|
||||
}
|
||||
|
||||
int DivePictureModel::rowCount(const QModelIndex &parent) const
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue