https://bugs.kde.org/show_bug.cgi?id=327865
--- Comment #9 from Christian Mollekopf <mollek...@kolabsys.com> --- The reason why everything gets dereferenced to zero, is because the FavortiteCollectionsModel sits on top of the EntityCollectionOrderProxyModel just like the other SelectionProxyModels that are part of StorageModel. So unless we have a workaround (like delaying the decrease of the refcount), the layoutChanged signal is our real problem. The layoutChanged signal get's emitted because the QSortFilterProxyModel baseclass of EntityCollectionOrderProxyModel detects that some indexes need to be resorted in it's sourceDataChanged slot, and that results in a layoutChanged signal. The dataChanged signal causing it in this case stems from Akonadi::EntityTreeModelPrivate::changeFetchState. However, the underlying models shouldn't change the order just because a new folder was selected in the view. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
