Bug 303440

Summary: the recently accessed/ search for should not appear above the "drives"
Product: [Applications] dolphin Reporter: m.wege
Component: panels: placesAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: markg85, nate
Priority: NOR    
Version: 2.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2012-07-12 21:44:10 UTC
With the implementation of rencently accessed and search in the places toolbar, the also new implemented section drives appears below all others. I find this rather not a useful order. In believe it would make much more sense to show the drives section below the folder section since it more used. I am not sure, if you agree, if so, the easiest thing would be to correct the order before release. If not, this is a wish: Make the order configurable.

Reproducible: Always
Comment 1 Frank Reininghaus 2012-08-07 15:38:57 UTC
Thanks for the report! I was away for a couple of weeks before the release, so I couldn't change it. I'll mark this report as a wish as you suggested - let's see what other users think about this.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:53 UTC
Resetting assignee to default as per bug #305719
Comment 3 Mark 2012-11-06 01:23:33 UTC
I think this depends on the user. In this case i agree with the reporter, but there might be very well people that disagree.

A better thing is imho to allow the re-ordering of the groups in the places panel to the users liking.
Comment 4 Frank Reininghaus 2012-11-06 06:36:27 UTC
(In reply to comment #3)
> A better thing is imho to allow the re-ordering of the groups in the places
> panel to the users liking.

Sure, but this would require quite a lot of code for (IMHO) a rather small benefit.
Comment 5 Nate Graham 2017-09-03 01:49:30 UTC
We'll get this for free once someone implements the oft-requested ability to re-order the sections: https://bugs.kde.org/show_bug.cgi?id=309621

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