Bug 436847

Summary:	Panel Suggestion: Recent Locations
Product:	[Applications] dolphin	Reporter:	Brand <cw>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	kfm-devel, nate
Priority:	NOR
Version:	21.04.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Brand 2021-05-10 03:55:27 UTC

In the side panel, where the places and network items are, it would be really helpful if we could also see recent locations we've been.

I'm not sure it is a part of Dolphin, but this would also be extremely helpful in the save dialogs, where we are saving to multiple folders. 

In both cases, it basically would give us one-click access to some of the most useful locations.

Comment 1 Brand 2021-05-10 03:57:47 UTC

And just to clarify, I know there is a recent locations link, but in this case, I mean an actual list of, say the last 10 or so folders we saved something to or opened a file in.

Comment 2 Nate Graham 2021-05-10 16:04:45 UTC

What's wrong with clicking on the "Recent Locations" item in the sidebar?

Comment 3 Brand 2021-05-10 16:24:33 UTC

(In reply to Nate Graham from comment #2)
> What's wrong with clicking on the "Recent Locations" item in the sidebar?

It isn't that there isn't anything "wrong" with it, but there would be benefits to a separate section:

1. Recent files doesn't always appear is KDialog
2. Having a list, like we do for Network, would be more consistent
3. It would be more user friendly. Currently, you can't rearrange the side panels, so it is already a scroll and two clicks to get inside of a recent folder, as opposed to it just appearing when you are looking at the dialog.

Comment 4 Nate Graham 2021-05-12 16:42:20 UTC

#1 is a bug which we can and should fix. :) See Bug 415019.
#2 is not really applicable as it is a different type of UI. Consistency between the same things in different contexts is desirable; consistency between different things in a similar context generally is not.
For #3 I understand what you mean, but I think if we fixed Bug 415019, it would probably solve 90% of the problem without adding a whole ton of new custom code.

Marking as a duplicate of Bug 415019, and once that's fixed, we can see if there's anything left to do to improve things.

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