From a169ca87cbe7b3ebe6f9ef24335f65ca64791116 Mon Sep 17 00:00:00 2001
From: Arno <arno@disconnect.de>
Date: Sat, 25 Feb 2017 18:45:49 +0100
Subject: Implement filtering

Well, as it turns out, QSortFilterProxyModel isn't the weapon of choice
for this. Implement it by creating a separate model which is populated
by SQL-Queries.
---
 beetplayerproxy.h | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'beetplayerproxy.h')

diff --git a/beetplayerproxy.h b/beetplayerproxy.h
index b50b972..69907ae 100644
--- a/beetplayerproxy.h
+++ b/beetplayerproxy.h
@@ -10,6 +10,10 @@ class BeetPlayerProxy : public QSortFilterProxyModel {
 
     protected:
         virtual bool filterAcceptsRow(int source_row, const QModelIndex &source_parent) const;
+
+    private:
+        bool hasValidChild(QModelIndex parent) const;
+        bool recurseChildren(QModelIndex parent) const;
 };
 
 #endif // BEETPLAYERPROXY_H
-- 
cgit v1.2.3-70-g09d2