Renaming A File Changes Its Position in List

[therube]

Renaming A File Changes Its Position in List (to the bottom)

Search for: 21 .txt

Finds:

Code: Select all

21228.txt
21229.txt
21310.txt
21999.txt

Drop down to 21228.txt & rename it to "21228.abc"

The list is reordered as such:

Code: Select all

21229.txt
21310.txt
21999.txt
21228.abc

[void]

This is by design.

Modified items now appear at the bottom of the list.

[therube]

Why?

With four items on my list, it's no big deal.
But how I found this is that I had a long list, renamed a file & it "disappeared".
I was like, huh?
So I renamed another file & it too disappeared.

Opened another instance I looked for those two files & sure enough, they existed.

Then went back to my first instance & realized where they went to.

What would be the rationale for putting them at the bottom?

To me, after a rename, which I'm apt to do quite often, I'm then forced to resort the current column, twice in succession, to get back to where I was.
You loose position, you loose context.
Highly counter-intuitive & unproductive IMO.

[void]

Why?

It is useful for tracking changes.

What should really happen is the renamed item should keep focus.

[therube]

Still not getting the gist of it?
Tracking changes in what kind of scenario?

And to drop to the bottom & totally change focus, that seems horribly wrong to me.

[therube]

*dont sort new results, add them to the bottom of the list (option)?

Definitely, option.

[void]

Still not getting the gist of it?
Tracking changes in what kind of scenario?

When a new file is created or an existing file is modified it is placed at the bottom of the list.

The focus lost is a bug and a fix is on my list of "things to do".

I have added: The option to keep new results or changed results sorted by name or path to my "things to do" list.

If sorting by anything other than name or path, the new results or changed results would have to be added to the end of the list for performance reasons.

[therube]

> The focus lost is a bug and a fix is on my list of "things to do".

Fixed in 643b.