QSortFilterProxyModel problem

[blukske]

You don't. The proxy model will call them to do a mapping from its indexes to source model indexes and the other way round.

I expected that as well. As it turns out, QSortFilterProxyModel maintains its own internal proxy_to_source & source_to_proxy mappings.

Have you checked in QAbstractProxyModel too?

I looked into it, but it requires a lot of additional signal/slot administration. Simply implementing the pure virtual functions is not enough, since changes to the source model are not propagated via the abstract proxy model to the view automatically. But I think I'll have to go that way now, as I'm ready to give up on QSortFilterProxyModel

My last try is to re-implement index() and data() using mapToSource & mapFromSource and see where that leaves me.

[wysota]

I looked into it, but it requires a lot of additional signal/slot administration.

I meant did you look into its source code while trying to find where mapFromSource and mapToSource are called.

Don't give up. All you need is to reimplement mapToSource and mapFromSource. And when I think of it, subclassing the abstract class directly could be the way to go, if you don't need the filtering and sorting functionality.

[blukske]

I meant did you look into its source code while trying to find where mapFromSource and mapToSource are called.

Don't give up. All you need is to reimplement mapToSource and mapFromSource. And when I think of it, subclassing the abstract class directly could be the way to go, if you don't need the filtering and sorting functionality.

I gave up . I checked QAbstractProxyModel's source, but again, mapFromSource/mapToSource are only called by mapSelectionFromSource/ToSource. Implementing them for either QAbstractProxyModel/QSortFilterProxyModel is not enough, because they are not getting called at all. I've got it working now by simply hiding/unhiding the columns in the tree view. Not the solution I wanted, but it works for now.

I'll try to implement a proper QAbstractProxyModel later on.