Bug 185188 - After deleting a file in Details view, the selection cursor disappears
Summary: After deleting a file in Details view, the selection cursor disappears
Status: RESOLVED DUPLICATE of bug 181214
Alias: None
Product: dolphin
Classification: Applications
Component: view-engine: details mode (show other bugs)
Version: 16.12.2
Platform: openSUSE Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-22 01:01 UTC by Alexander Neundorf
Modified: 2017-09-03 16:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Neundorf 2009-02-22 01:01:45 UTC 
Version:            (using KDE 4.1.3)
Installed from:    SuSE RPMs

Usually, when navigating in the detailled view using up/down, this also selects the current file. 
When I then delete the file, after that no file is marked as selected. I have to press up/down once to see a file selected again.
I had the impression that this selection would appear at a random location, but now I saw that after deleting the file, at least the keyboard cursor, i.e. the dotted line around the file name is drawn. This is very easy to overlook.

I'd suggest to mark this file as selected automatically, so it is easy to see where keyboard focus is.

Alex
Comment 1 FiNeX 2009-02-23 22:48:49 UTC 
On current trunk the focus (dotted rectangle) is placed to the file before the one deleted.
Comment 2 Alexander Neundorf 2009-02-23 23:55:25 UTC 
So current trunk behaves the same as 4.1.3.
The dotted rectangle is really hard to see on my notebook, selecting this item automatically would help with this.

Alex
Comment 3 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:20:04 UTC 
Resetting assignee to default as per bug #305719
Comment 4 Nate Graham 2017-09-03 14:05:12 UTC 
Yes, when an item is deleted, the selection cursor should automatically move to the next available item.
Comment 5 Nate Graham 2017-09-03 16:35:11 UTC 

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