[Interest] Design Issue with QAbstractItemModel & QTreeView

[Sébastien Le Ray]

Hi

Thanks for your answer

I know about xxxInsertRow but these are meant to be called by the model 
(or at least by a class that has knowledge of the model). The question 
is how to properly call it when the only notification you get from the 
data is "this row was added|removed".

Regards


Le 04/08/2016 à 19:33, Igor Mironchik a écrit :
> Hi,
>
> I'm not sure what are you talking about. But what about
> beginInsertRows() and endInsertRows()? Between this methods you should
> add new data, and this data can has child rows.
>
> What is the problem?
>
>
> On 04.08.2016 19:48, Sébastien Le Ray wrote:
>> Hi list,
>>
>> I'm currently designing an application which presents its data in a
>> tree. I have a QAbstractItemModel making a bridge between these data
>> and the view, so far so good.
>>
>> However I'm stuck when it comes to react to underlying data structure
>> changes, specifically when rows are added and removed. Model has to
>> react before and after the row is added, however, the only
>> information it gets is "row added" signal. Worse, adding a row can
>> add the row and some subitems (some objects creates mandatory children).
>>
>> What is the proper way to deal with this? Should I have some kind of
>> proxy between the data and the mode?
>>
>> Regards