-
Committer:
Tarmac
-
Author(s):
Albert Astals
-
Date:
2013-08-21 11:31:43 UTC
-
mfrom:
(80.1.3 dee-qt)
-
Revision ID:
tarmac-20130821113143-x8jf8gsb12ngesjl
Be a better behaved QAbstractListModel
That means:
* decrement/increment the count between the begin/end calls
* Add a workaround so that data() ignores the not really removed row after endRemoveRows has been called
We still are not good behaved in the fact that we call beginInsertRows
after the model has been internall modified, but luckily it seems
not much people listens to that signal's data
We also rely on the fact that nothing will call data() between us
resetting m_rowBeingRemoved to -1 at the end of DeeListModelPrivate::onRowRemoved
and the internal dee model actually removing the row.
Approved by PS Jenkins bot, Michal Hruby.