[Interest] Design Issue with QAbstractItemModel & QTreeView

[Sébastien Le Ray]

Le 05/08/2016 à 17:47, john at wavemetrics.com a écrit :
>> When you say "packaging", you mean that you have a wrapper around the underlying data (something like a TreeItem class that "caches" data)
> I mean preparing the presentation of the data.

Which mean? :D
>> Main issue is not on adding rows (this you can indeed call begin while data is already added), issue is on removal since beginRemoveRows needs to access to the to-be-removed row, which is an issue if row has already been removed
> Why does removing a row require access to the (now gone) data?

Don't know, just experienced it, TreeView performs some kind of size 
computation on the to-be-removed-row-which-is-in-fact-already-removed 
and all blow up