After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315390 - icon view and reversed order behaviour
icon view and reversed order behaviour
Status: RESOLVED DUPLICATE of bug 310919
Product: nautilus
Classification: Core
Component: Views: Icon View
2.10.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-06 20:33 UTC by Christian Rudh
Modified: 2005-09-06 22:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Christian Rudh 2005-09-06 20:33:00 UTC
Please describe the problem:
I have a folder with some files and some folders. Some of both the files and the
folders have an emblem (same emblem on all). I also have "Sort folders before
files" enabled in the nautilus preferences.

Then I use "Arrange items" in the folder and set it to "By Emblems" and
"Reversed Order".

Steps to reproduce:


Actual results:
This displays the files without emblems first, the files with emblems second,
the folders without emblems third and the folderd with emblems last.

Expected results:
Since I thought the global nautilus setting of "Sort folders before files"
should take precedence I expected the behaviour to be: Folders without emblems
first, folders with emblems second, files without emblems third and files with
emblems last.

Does this happen every time?
Yes.

Other information:
Maybe others feel that the way now is the correct way, but with the current
behavior the reversed sorting order of all the sorting types is unusable if you
want the folders before the files always. And it makes the preference setting of
"Sort folders before files" meaningless if you have a reversed order.
Comment 1 Christian Neumair 2005-09-06 22:32:53 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 310919 ***