Bug 185192

Summary:	status bar and info pane don't react to changes after file renames (detailled view)
Product:	[Applications] dolphin	Reporter:	Alexander Neundorf <neundorf>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED FIXED
Severity:	normal	CC:	byron, finex, rakuco, schaefer.frank
Priority:	NOR
Version First Reported In:	16.12.2
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander Neundorf 2009-02-22 01:20:12 UTC

Version:            (using KDE 4.1.3)
Installed from:    SuSE RPMs

If I navigate to some file using the up/down keys, and the mouse cursor is not over the dir view, then the status bar and the info pane show information for the currently selected file, this is ok.

Now I press F2 to rename a file.
After that, the renamed file is still selected and has keyboard focus.

But if I now move up or down using the keyboard, the selection moves, which is correct, but neither the status bar nor the info pane react to this. I first have to move the mouse cursor over the dir view and back from it, then the status bar and info pane react again to movements done with the keyboard.

Alex

Comment 1 Raphael Kubo da Costa 2009-08-05 03:33:45 UTC

This also happens in the Icons view, but not in the Columns view.

Comment 2 Raphael Kubo da Costa 2009-08-05 03:54:37 UTC

Actually, I've just been able to reproduce this using the Columns view as well.

Comment 3 FiNeX 2009-08-05 10:04:35 UTC

Moving the selection with the arrow keys, still doesn't update the information panel.

The information panel displays the info from the hovered item or, if the mouse cursor is out of the view, it displays the current dir info.

Comment 4 Frank Schaefer 2009-11-23 12:03:51 UTC

I can confirm this, it's still present in 4.3.3.
Always reproducible.

Comment 5 Frank Reininghaus 2009-12-28 00:00:14 UTC

*** Bug 220069 has been marked as a duplicate of this bug. ***

Comment 6 Raphael Kubo da Costa 2010-01-10 23:49:19 UTC

This seems to have been fixed -- maybe by r1070800 (bug 212797 looks similar to this one).