Bug 383641 - F2 (Rename) on file which changed its position while quickly selecting with cursor up/down key shows wrong content
Summary: F2 (Rename) on file which changed its position while quickly selecting with c...
Status: RESOLVED DUPLICATE of bug 331236
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 17.04.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-17 17:19 UTC by Gregor Mi
Modified: 2017-11-12 19:10 UTC (History)
3 users (show)

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


Attachments
demo1 (23.42 KB, image/gif)
2017-08-17 17:26 UTC, Gregor Mi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2017-08-17 17:19:54 UTC
The following behaviour hinders renaming files using the keyboard in quick succession.

First the correct behaviour when typing in a slow fashion:

1) Have two files "a" and "b" in Details View
2) Select "b", press F2, rename it to "1b", press Enter
3) Observe that after a short moment the file "1b" moves above "a".
4) Use cursor key to select "a", press F2 and rename. OK

Now this happens when we speed up things:

1) Again, have two files "a" and "b" in Details View
2) Select "b", press F2, rename it to "1b", press Enter
3) Now, before file "1b" moves above "a", be quick to press Cursor up (selects "a") and then press F2
4) Observe that now the first file in the list is in renaming mode with the text "a" (*) selected. The second file is also named "a".

(*) the text "a" is wrong. It should be "1b". One could think one would rename the file "a" while in reality "1b" is renamed again.
Comment 1 Gregor Mi 2017-08-17 17:26:20 UTC
Created attachment 107334 [details]
demo1

add a little screencast to demonstrate
Comment 2 Sebastian Frei 2017-10-23 12:26:32 UTC
I guess this is a duplicate of 331236.
Comment 3 Nate Graham 2017-11-12 19:10:16 UTC

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