6

I'm implementing a Qt based tree view, where the view is a QTreeView-based class and the model is a QAbstractItemModel-based class. The tree is supposed to have millions of nodes in it. I'm implementing a filtering mechanism, in which filtered out nodes are just hidden in the tree view. (I don't want to use QSortFilterProxyModel)

The model's internal data structure looks somewhat like this.

class MyTreeItem
{
 ...
 private:
      QList<MyTreeItem *> _children;
      bool                _isHidden;
 };

 class MyTreeModel : public QAbstractItemModel 
 {
  ...
  private:
       MyTreeItem * _rootNode;
  };

I can determine whether a particular node (MyTreeItem*) should be filtered while the model data structure is being populated. So I want to let the QTreeView know that this item should be hidden while populating the data structure, rather than traversing the entire tree again and hiding rows after populating.

Honestly, I'm in the design stage, so I don't have any real code. My requirement is, while populating the data structure, I will determine whether the current node should be filtered, and if so, will set the flag _isHidden. But I'm not sure how to let the view know when to hide the row by calling QTreeView::setRowHidden() or by some other means.

Please share your thoughts on best way do this. Thanks.

susiriss
  • 83
  • 1
  • 5
  • Why don't you want to use [`QSortFilterProxyModel`](http://doc.qt.io/qt-5/qsortfilterproxymodel.html)? From the description you've given it's quite obviously the correct tool for the job. – G.M. Dec 21 '17 at 10:03
  • @G.M. My project team has decided that using `QSortFilterProxyModel` is performance burden. So it should be out of the equation. – susiriss Dec 21 '17 at 12:38
  • If you don't want the item visible in the model, why include it in the first place? Just don't add it. – Maxim Paperno Dec 22 '17 at 04:38

1 Answers1

7

There is no built-in data flags to hide a cell (or row) in the standard Qt model item views. You can disable items or make the non-selectable, but not hide them entirely.

You could of course loop through your model and call QTreeView::setRowHidden() manually but you indicate you don't want to do that, and I would tend to agree (it would be much more efficient and practical to use a proxy model).

So you would most likely want to subclass one of the item views to get your desired effect and filter them there based on your custom flag. There is also the item delegate route (also set at the view level, not the model), so you might be able to filter out fields there by simply not painting them (but I've never tried that).

Or as suggested in the comments use QSortFilterProxyModel which is designed exactly for what you're asking (and really isn't going to add noticeable overhead to a typical GUI application on modern hardware). You could also write your own proxy model. You can use only the parts of QSortFilterProxyModel code which you need, for example.

Or as I also already suggested, simply don't include the rows you don't want when building the model.

Maxim Paperno
  • 4,485
  • 2
  • 18
  • 22
  • Why I'm hesitant to not include the rows to be hidden, when building the model is that whenever the filters change, I'll need to rebuild the entire model again, since the data source for the model is a sequential source. That looks like an overkill to me. From your suggestions, subclassing the view (QTreeView in my case) seems a better options to me. `QAbstractItemView::isIndexHidden()` looks like the method to override in this case. Any idea about using this method ? Thanks for taking time for the helpful answer. – susiriss Dec 22 '17 at 06:16
  • I think `isIndexHidden()` is just a way to query the status. I've never done what you're trying so I'm not sure which would work best. Looking at the code for [`QTableView`](https://code.woboq.org/qt5/qtbase/src/widgets/itemviews/qtableview.h.html), the `setRowHidden()` just calls `setSectionHidden()` on the vertical header. Then e.g. in the [QTableView::paintEvent()](https://code.woboq.org/qt5/qtbase/src/widgets/itemviews/qtableview.cpp.html#1343) it checks the vertical header to see if the row should be skipped. So I wonder if you may be better off re-implementing a `QHeaderView` instead. – Maxim Paperno Dec 22 '17 at 08:10