Total Commander

[jdmarch]

Task: after feeding search results to a listbox, sort by filename.
Problem: the built-in "Name" column includes path in this context.

First attempt: include a custom column [=tc.path]. Now the"Name" column automagically displays only filenames, not paths. Great!
Problem: But the "Name" column still sorts by the path which it is not displaying, rather than by the filename that it is displaying.
Bug?: This seems like a bug to me; you expect a column to sort on its visible contents.

Next attempt: Use custom columns [=tc.name] and/or [=tc.ext]., and try to disappear the built-in Name and Ext column.
Problems: The built-in columns Name and Ext cannot be moved or made to disappear. Also the useful filetype/folder icons are in Name but not in [=tc.name].

Final attempt: Apparently the best I can do is to make Name column 10 units wide and make Ext column 20 units wide, which causes some pixel pollution between these columns, but not too bad. After these comes [=tc.name], which is a counter-intuitive display order (extension before name).

Proposal: Make the Name column sort on its displayed contents.

This has been reported before in much less detail, but I did not see any discussion of it. See the last post of: http://ghisler.ch/board/viewtopic.php?t=7268

[ghisler(Author)]

This is indeed intentional to get consistent sort orders for full view and custom columns view. I have considered to sort by displayed names also for other fields or field parts, but it would lead to a big number of problems (e.g. when sorting by parts of numeric fields)...
_________________
Author of Total Commander
http://www.ghisler.com

[jdmarch]

Thanks. I think I understand you, but of course by holding to one kind of consistency you've introduced an inconsistency with standard user expectations, which is that a plain filename column will sort on plain filename. Maybe an option...?

[karlchen]

Hello, jdmarch.

[jdmarch]

Karl, thank you for the thought and the work. Unfortunately this does not make an improvement from my perspective. Unless the unremoveable EXT column is widented to 20, it pollutes the following name column. And once I've widened it, there's no reason (at least from my perspective) to use tc.fullname instead of tc.name -- it just wastes screen space.

For the record, this seems to be my best workaround:

[karlchen]

Hello, jdmarch.

As soon as I have got the chance and time, I will post a screenshot illustrasting what the customfields view "Search Results" looks like here. A screenshot may ease undertanding a lot.

The unremovable EXT column does not pollute anything here. All it will hold here is two little dots.

The tc.fullname is used to make sure that filename and extension are displayed in the right order, filename first, extension second, without having to insert another column for the extension.

Maybe the crucial factor which decides whether you get what you want or whether you don't when using the view "Search Results" is this setting:
Configuration => Options => Display => Tabstops:
Show file extensions
(*) directly after filename
(_) aligned (with tab)

Extensions are displayed directly after the filename here.

Kind regards,
Karl

[Lefteous]

The generic problem here is that only full paths can be unique. When using such a custom column view a secondary sort order is required. TC already has such a mechanism. There should be a way to show the search result not only in a preferable (column) view but also in a useful sort order - of course without manual activity.


2karlchen

[karlchen]