Use shift-click to mark several files in the file list. Do a Delete Permanently.
1) The cursor should position on the first file after the deleted group. It positions several files lower than that and equal to the number of files deleted.
Don't move the repositioned cursor. Just use another shift-click to mark another range of files lower down in the list.
2) You will mark files beginning at the top of the file list - including directories!
WinXP
FCXE 0.0.0.570 public preview
570 - Cursor indexing after multiple delete - 2 bugs
-
- Posts: 14
- Joined: 13.12.2009, 19:31
Re: 570 - Cursor indexing after multiple delete - 2 bugs
I can confirm the first bug, but the second bug does not occur for me -- instead, the second step simply repeats the first bug. (The first bug occurred in my previous version as well, 550.)
Furthermore, the bug occurs for me with any deletion -- whether permanant or to the Recycle Bin.
I would describe the first bug in this way: The cursor or focus remains in the same place in the folder/file list before and after the deletion. So, for example, if the selection ENDS on the fifth item, then it will be on the fifth item after the deletion.
I agree with PhiloVance that the expected behavior is for the cursor to be located on the first item after the deleted group. Or in other words, if the selection BEGINS on the third item, then it should be on the third item after deletion. I believe that was how FC 2009x worked.
In short, the problem seems to be which point FC XE is referencing for cursor placement after the deletion: the end of the selection (bug) rather than the beginning of the selection (correct).
FC XE 570, Win 7 HP x64
Furthermore, the bug occurs for me with any deletion -- whether permanant or to the Recycle Bin.
I would describe the first bug in this way: The cursor or focus remains in the same place in the folder/file list before and after the deletion. So, for example, if the selection ENDS on the fifth item, then it will be on the fifth item after the deletion.
I agree with PhiloVance that the expected behavior is for the cursor to be located on the first item after the deleted group. Or in other words, if the selection BEGINS on the third item, then it should be on the third item after deletion. I believe that was how FC 2009x worked.
In short, the problem seems to be which point FC XE is referencing for cursor placement after the deletion: the end of the selection (bug) rather than the beginning of the selection (correct).
FC XE 570, Win 7 HP x64
Re: 570 - Cursor indexing after multiple delete - 2 bugs
Wonderful -- thanks very much, Marek.
Who is online
Users browsing this forum: No registered users and 76 guests