Merging Rows of QStandardItemModels to Show in One QTreeView

[anda_skoa]

Option #1 isn't really doable due to the low level nature of the values (they have to stored in statically allocated arrays indexed by an enum),

I am afraid I don't understand.

Even if the source data structure is not capable of providing all information (which sounds doubtful), you could copy the data into a structure that does, just like you are doing now.

If I have a single underlying model, and a QSortFilterProxyModel for each type (which I already do, except the current mapping is 1 to 1),
how would my connection of type-specific callbacks to QStandardItemModel::itemChanged be changed?

Not sure what you mean, each type's filter model will be a separate signal source.

Would I then have to store a type column into the leaf nodes (so the value items will be 4 columns long), then on any itemChanged
for the whole model, I dispatch based on the type stored?

Don't you already know the type of an entry? How would you otherwise even filter for a type?

Cheers,
_