Just found out about QSortFilterProxyModel::filterAcceptsColumn which provides an integer for the column-index and hence suits my usecase perfectly. Still unsure why I couldn't get it to work with map(From/To)Source though

After thinking about this problem more and looking at the interface for QAbstractProxyModel, I am beginning to think that a subclass of a proxy model is not the answer. I am wondering if the best course of action would be to create a new model which keeps a pointer to my base model. Every time the various data changed signals are emitted from the base model, my "proxy" model determines if a new sequence has been found. It then keeps track of all the various sequences in its own internal data structure which keeps QPersistenModelIndex indexes into the base model. Then my "proxy's" data() method would use these indexes to get the real data from the underlying model but parsed into the correct format.

Do this sound like a better approach?

In this case, I am also wondering how to display my data as a table where each row could have a different number of columns. Perhaps I could keep track of the row with the maximum number of columns and return this in columnCount()? Then my data() method would just return QVariant() for columns that don't exist in a given row.

That I don't know.

If you have an interesting re-usable model to share then you can do a submission.

@Christian-Ehrlicher said in Support for QStandardItem proxies?:

But only when Qt was compiled in debug mode

Yes, as the docs say using invalid indexes remains undefined behaviour, I am just trying to help users spot these cases

@VRonin said in Smarter way to get a list of children in Tree Model:

the overridden data is to store somewhere the level in the original tree before it gets flattened by KDescendantsProxyModel.

I don't believe you need that. Pushing a tree model to a list/table view should give you list/table with the root-level items (speculation again!). In my mind it should be just enough to "move" the root of the model before giving it to the view.

I didn't feel like going through building a QAbstractProxyModel from scratch

Well, yes, I can see why, but if you think about it, most of your methods should turn out trivial (more or less) - similarly to the identity proxy model.

Kind regards.

Awesome! Thank you @VRonin .

Yeah but the user also want to be able to reorder things as he wants, not just sort (ie, put this row here, drag all my selection at this position, invert these two rows, ...)

Thanks for the reply, I will take this to the mailing list!

@ThatDud3 well, Qt 5.5 have been released, but I don't see nothing about proxy in QWebEngineSettings XD It is real problem...

Hi thanks,

Finally I found libproxy, I will try to see if it does what I want.

Best regards,
Alexis.