Summary: | When sorting files by "Size", the name is used as a fallback for sorting files with equal size, but renaming files does not cause a resorting | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Frank Reininghaus <frank78ac> |
Component: | view-engine: general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 4.11.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kde-baseapps/6b375d2e26312ff032da072d93e92a8e080a1361 | Version Fixed In: | 4.11.1 |
Description
Frank Reininghaus
2013-08-14 22:05:44 UTC
Git commit 6b375d2e26312ff032da072d93e92a8e080a1361 by Frank Reininghaus. Committed on 14/08/2013 at 22:07. Pushed by freininghaus into branch 'KDE/4.11'. Make sure that the sort order is correct after renaming KFileItemModel::setData() should not only cause a resorting when the sort role is changed. The name is always used as a fallback if the sort role of multiple files is equal, therefore, renaming a file can change the correct order of the files even if the files are not sorted by "name". Unit test included. FIXED-IN: 4.11.1 REVIEW: 111721 M +24 -2 dolphin/src/kitemviews/kfileitemmodel.cpp M +25 -0 dolphin/src/tests/kfileitemmodeltest.cpp http://commits.kde.org/kde-baseapps/6b375d2e26312ff032da072d93e92a8e080a1361 |