Filesystem browser: "Go up"-arrow not working after "Current document folder"
dhaumann at kde.org
Wed Sep 6 20:17:29 UTC 2017
On Wed, Sep 6, 2017 at 9:52 PM, Alexander Neundorf <neundorf at kde.org> wrote:
> On 2017 M08 29, Tue 22:54:17 CEST Alexander Neundorf wrote:
>> I started to look into this, but didn't get far yet.
>> In Kate I'm using the Filesystem Browser, and I use the "Current document
>> folder" action (syncFolder) often.
>> Directly after the syncFolder action the "Go up" action does not work, it
>> does nothing. After chosing a different directory in another way, "Go up"
>> works again.
>> I'm a bit lost... is this maybe an issue in KDirOperator ?
> any hints where to start looking ?
The action is called "up". It is referenced only once in the
filesystembrowser source code. Besides that, you can find it in
frameworks/kio/src/filewidgets/kdiroperator.h/cpp. Syncing the current
folder finally calls KDirOperator::setUrl(). It seems after this call,
it does not work anymore. If I comment this line out (line 221
katefilebrowser.cpp), syncing does not work anymore, but up will
always work. So yes, invoking setUrl() breaks the action - for
whatever reason. Seems a bug in kdiroperator.
Debugging shows that KDirOperator::cdUp() may not work correctly, or
if it does, the "// already set" case in KDirOperator::setUrl()
matches and an early return happens.
Not sure what is really going on here, but I currently have no time to
More information about the KWrite-Devel