Bug 389305

Summary:	kdialog --getexistingdirectory doesn't start in startfolder
Product:	[Applications] kdialog	Reporter:	dutchkind
Component:	general	Assignee:	Brad Hards <bradh>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kde
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:	https://commits.kde.org/plasma-integration/af9284852c492ac4db75a9f5ada566ff324abf04	Version Fixed/Implemented In:	5.12.0
Sentry Crash Report:

Description dutchkind 2018-01-22 08:28:58 UTC

When I invoke kdialog --getexistingdirectory /home/user/Dropbox/ I expect to see the dialog start IN the startfolder used as argument, but I am presented with a directory tree of the root file system instead and have to manually browse for the correct location. For non techie users this is a problem to find their way. This has been in kdialog since many months, and I hoped it would get fixed. So hopefully someone can have a look into it.

Comment 1 Kai Uwe Broulik 2018-01-22 10:08:14 UTC

It seems to expand only the first level of folders, if I choose /home/foo/bar it expands "home", if I choose /usr/share/applications it expands "usr"

Comment 2 Kai Uwe Broulik 2018-01-25 09:46:15 UTC

Git commit af9284852c492ac4db75a9f5ada566ff324abf04 by Kai Uwe Broulik.
Committed on 25/01/2018 at 09:45.
Pushed by broulik into branch 'Plasma/5.12'.

[KFileTreeView] Manually expand tree when model tells us to

It seems just setting the current index isn't enough to expand all the way down.
FIXED-IN: 5.12.0

Differential Revision: https://phabricator.kde.org/D10016

M  +1    -0    src/platformtheme/kfiletreeview.cpp

https://commits.kde.org/plasma-integration/af9284852c492ac4db75a9f5ada566ff324abf04

Comment 3 dutchkind 2018-01-26 07:35:06 UTC

Thanks! I will see it when it becomes available in Opensuse tumbleweed.