Well, yeah. A model reset tells all views that everything they know is wrong, and they have to go back and ask for it all again. And the method lives in the view and not the model because you may not want all views of the model to have this behavior.Also seems to be reset when the model is reset which is also annoying.
The best solution is to probably derive from QTreeView and override reset() and/or dataChanged(). Call the base class method first, then add your first row spanning.




Reply With Quote

Bookmarks