mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
filter: reset shown_dives in filter
The shown_dives variable was reset by the dive_list code. Arguably, the filter should keep track of the number of shown dives, so move the resetting there. This means adding a new "reset()" member function to the filter and call that instead of "updateAll()" when the core data is reset. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
parent
dea1ef84d5
commit
e80c0d2c60
4 changed files with 15 additions and 8 deletions
|
@ -706,7 +706,7 @@ DiveTripModelTree::DiveTripModelTree(QObject *parent) : DiveTripModelBase(parent
|
|||
|
||||
void DiveTripModelTree::populate()
|
||||
{
|
||||
DiveFilter::instance()->updateAll(); // The data was reset - update filter status. TODO: should this really be done here?
|
||||
DiveFilter::instance()->reset(); // The data was reset - update filter status. TODO: should this really be done here?
|
||||
|
||||
// we want this to be two calls as the second text is overwritten below by the lines starting with "\r"
|
||||
uiNotification(QObject::tr("populate data model"));
|
||||
|
@ -1475,7 +1475,7 @@ DiveTripModelList::DiveTripModelList(QObject *parent) : DiveTripModelBase(parent
|
|||
|
||||
void DiveTripModelList::populate()
|
||||
{
|
||||
DiveFilter::instance()->updateAll(); // The data was reset - update filter status. TODO: should this really be done here?
|
||||
DiveFilter::instance()->reset(); // The data was reset - update filter status. TODO: should this really be done here?
|
||||
|
||||
// Fill model
|
||||
items.reserve(dive_table.nr);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue