Dive list: make filter model aware of its source

The data-flow from C-core to list-view is as follows:

C-core --> DiveTripModel --> MultiSortFilterModel --> DiveListView

The control-flow, on the other hand, differs as DiveListView
accesses both MultiSortFilterModel and DiveTripModel, whereas
MultiSortFilterModel is mostly unaware of its source model.

This is in principle legitimate, as the MultiSortFilterModel might
be used for different sources. In our particular case, this is
not so. MultiSortFilterModel is written for a particular use case.

Therefore, model control-flow follow after data-flow: Let MultiSortFilterModel
set its own source model and DiveListView access the MultiSortFilterModel,
which then manages its source model.

This is not bike-shedding, but will enable a more flexible and
higher-performance sorting.

Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>

1 files changed, 3 insertions, 0 deletions

diff --git a/qt-models/filtermodels.h b/qt-models/filtermodels.h
index f962386a1..f579df1a9 100644
--- a/qt-models/filtermodels.h
+++ b/qt-models/filtermodels.h
@@ -2,6 +2,8 @@
 #ifndef FILTERMODELS_H
 #define FILTERMODELS_H
 
+#include "divetripmodel.h" // For DiveTripModel::Layout. TODO: remove in due course
+
 #include <QStringListModel>
 #include <QSortFilterProxyModel>
 #include <stdint.h>
@@ -132,6 +134,7 @@ slots:
 	void startFilterDiveSite(struct dive_site *ds);
 	void stopFilterDiveSite();
 	void filterChanged(const QModelIndex &from, const QModelIndex &to, const QVector<int> &roles);
+	void setLayout(DiveTripModel::Layout layout);
 
 signals:
 	void filterFinished();