From c872dcbda9b0fbcd945a7917ae9e4b3cb61f347c Mon Sep 17 00:00:00 2001 From: Peter Penz Date: Sun, 30 Oct 2011 20:57:50 +0100 Subject: Fix sorting-issues when value of a sort-role has been changed If the value of a sort-role has been changed, emitting the signal itemsChanged() is not sufficient as from the KItemModelBase point of view an item has been moved or deleted/reinserted. Corresponding to the unit-test KFileItemModel::setData() respects this case correctly now, however there are some minor visual animation issues left that (hopefully) should not be tricky to solve. --- src/kitemviews/kfileitemmodel.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/kitemviews/kfileitemmodel.h') diff --git a/src/kitemviews/kfileitemmodel.h b/src/kitemviews/kfileitemmodel.h index e34503ebb..8bf299003 100644 --- a/src/kitemviews/kfileitemmodel.h +++ b/src/kitemviews/kfileitemmodel.h @@ -160,6 +160,9 @@ private: TypeRole, DestinationRole, PathRole, + CommentRole, + TagsRole, + RatingRole, IsDirRole, IsExpandedRole, ExpansionLevelRole, @@ -201,6 +204,7 @@ private: QList > sizeRoleGroups() const; QList > dateRoleGroups() const; QList > permissionRoleGroups() const; + QList > ratingRoleGroups() const; QList > genericStringRoleGroups(const QByteArray& role) const; /** -- cgit v1.3.1