1.5 Alpha: Secondary sort (Size DESC -> Date DESC) failing to execute on files

[Br0Haha]

Hi David,

I am running Everything 1.5.0.1418b (x64) and am trying to achieve a dual column sort: Size (Descending) as primary, and Date Modified/Created (Descending) as secondary. My goal is to find my largest MP4 files and have the newest ones show on top within those size groups.

However, neither the UI interactions, the Advanced Sort menu, nor the search bar functions are successfully executing this dual sort.

What I have tried:

• Advanced Sort Dialog: Setting Sort by: Size (Descending) and Then by: Date Created (Descending) as shown in my attached screenshot. It does not apply to the search results.
  
  Search Bar Syntax: I've tried passing sort:size-descending secondary-sort:"date modified" secondary-sort-descending: as well as variations using sort:size-desc and sort-secondary:. The secondary sort parameter appears to be ignored entirely.
  
  Index Settings: I have verified that "Fast date modified sort" and "Fast size sort" are both enabled under Tools -> Options -> Indexes.

It feels like the secondary sort logic is colliding with the folder hierarchy rules (e.g., Folders on Top vs. Mix Files and Folders), completely discarding the secondary file date criteria behind the scenes.

Is this a known limitation with size/date secondary indexing in current 1.5 alpha builds, or is there a specific INI/Advanced configuration required to break this structural lock?

Thank you!

[void]

Large mp4 files are going to have unique sizes.
Your secondary sort is not going to influence the sort order much, if at all.
Results will mostly be sorted by size.

It feels like the secondary sort logic is colliding with the folder hierarchy rules (e.g., Folders on Top vs. Mix Files and Folders), completely discarding the secondary file date criteria behind the scenes.

Shift clicking a column header will set the secondary sort and show folders first.
Mixing files and folders is disabled when using a secondary sort.

Is this a known limitation with size/date secondary indexing in current 1.5 alpha builds, or is there a specific INI/Advanced configuration required to break this structural lock?

Could you please give an example of the sizes and date modified in the results and your desired sorting.



Try grouping sizes and then sorting those groups by date modified, for example:
100MB groups:

a:=INT($size:/100000000) sort:a-descending;date-created