View Issue Details

IDProjectCategoryView StatusLast Update
0001907Double CommanderGraphical user interfacepublic2021-09-05 15:10
Reporterkandrey89 Assigned ToAlexx2000  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
ProjectionnoneETAnone 
PlatformMacOSOSXOS Version10.12.6
Product Version0.7.8Product Build2/24/2017 
Target Version0.8.4Fixed in Version0.8.4 
Summary0001907: Delete Operation Resets Cursor Position in the Navigation Pane
DescriptionDelete operation of a file changes the cursor selection position to change to the 1st item in the file list which is always a '..'.
Please change it so that the cursor position goes to the next file in the list, that way when I am deleting 999th file, my navigation pane does not scroll all the way back to the 1st file, and I have to scroll back to 1000th file.
Steps To ReproduceIn any location with many items (files/folders), select for ex. a 10th file in the list (Brief List).
Delete that file.
You will notice the the cursor selection is now on 1st file in the list, not the 11th from original list, or the 10th from the new updated list post-deletion.
TagsNo tags attached.
Fixed in Revision8156,8235
Operating systemMacOSX
WidgetsetQT4
Architecture64-bit

Relationships

duplicate of 0001236 closedAlexx2000 Cursor jumps to the top after file deletion 

Activities

kandrey89

2018-06-29 07:26

reporter   ~0002648

Alex, can you fix this please? Super annoying when trying to delete some files when you don't want to select multiple files or can't.

Alexx2000

2018-06-29 07:42

administrator   ~0002650

Theoretically, this is fixed in the current development version, 0000831.

kandrey89

2018-06-30 04:58

reporter   ~0002652

The issue is still there in v0.8.3 rev 8160.
Just tried it, deleting a file causes the cursor to go to the first item.

Alexx2000

2018-06-30 10:48

administrator   ~0002654

Last edited: 2018-06-30 13:18

Current development version is 0.9.0, revision >= 8156. You can get it from "Snapshots" page to test.

kandrey89

2018-07-03 00:26

reporter   ~0002655

OK, it's fixed in v0.9.0 8189, I don't understand how the rev works, shouldn't v0.8.3 rev8160 have the 8156 rev fix?

Alexx2000

2018-07-04 14:04

administrator   ~0002663

No, it is two parallel branches: 0.8.x and 0.9.0. When some fix done then it go to 0.9.0. If fix confirmed then it will be merged to next 0.8.x version.

Issue History

Date Modified Username Field Change
2017-08-28 22:45 kandrey89 New Issue
2018-06-29 07:26 kandrey89 Note Added: 0002648
2018-06-29 07:42 Alexx2000 Note Added: 0002650
2018-06-30 04:58 kandrey89 Note Added: 0002652
2018-06-30 10:48 Alexx2000 Note Added: 0002654
2018-06-30 13:18 Alexx2000 Note Edited: 0002654
2018-06-30 13:18 Alexx2000 Status new => feedback
2018-07-03 00:26 kandrey89 Note Added: 0002655
2018-07-03 00:26 kandrey89 Status feedback => new
2018-07-04 14:04 Alexx2000 Note Added: 0002663
2018-07-04 14:04 Alexx2000 Fixed in Revision => 8156
2018-07-04 14:04 Alexx2000 Status new => resolved
2018-07-04 14:04 Alexx2000 Resolution open => fixed
2018-07-04 14:04 Alexx2000 Assigned To => Alexx2000
2018-07-20 22:27 Alexx2000 Target Version => 0.8.4
2018-08-04 15:27 Alexx2000 Fixed in Revision 8156 => 8156,8235
2018-08-04 15:27 Alexx2000 Fixed in Version => 0.8.4
2018-12-01 15:59 Alexx2000 Relationship added duplicate of 0001236
2021-09-05 15:10 Alexx2000 Status resolved => closed