DOPUS sort vs. other apps (previous/next file) -

I have noticed a discrepancy between DO and Explorer/other windows apps when it comes to sorting.

For instance, if I have two (or more) files named:

example.txt
example 2004.txt

DO will list them in the order above. However Explorer does it the other way around. I barely use Explorer anymore but OTHER apps are using the Explorer order when skipping to next/previous file, which throws me for a loop when I'm cleaning up images/photos folders.

I have not found a setting in DO to use that Explorer/Windows sort order. Did I miss it? Thanks.

1 Like

Folder Format > Sorting > Sort name and extension separately

I tried that and it made no difference. Am I looking in the right place (image)?

How would sorting name and extension separately affect the example, though? The extension is the same; the difference is one of the files has a space followed by numeral in the name part.

Try it via the Folder menu in the lister, to see if it gets what you want. (See the first FAQ in the menus at the top of the forum for how to save that change for all folders, if it is what you want.)

Because Explorer is sorting the strings as

  • example.txt
  • example 2004.txt

While Opus is sorting them as:

  • example; .txt
  • example 2004; .txt

IMO, Explorer's order makes less sense, but it's up to you which you use in Opus. Which of these orders makes more sense to you?

Opus (with separate names and extensions on):

File.txt
File 2.txt
File 3.txt

File Explorer:

File 2.txt
File 3.txt
File.txt

File Explorer does that because a space comes before a dot, but it's a far worse way to order things IMO.

3 Likes

I do agree with you completely. There are times however when I need to deal with large number of files through 3rd party programs (irfanview, zoom player...) whose next/previous file logic is based on the standard Windows sorting, so I wanted those folders to be sorted the same way.

To clarify, I was wondering why the option is named the way it is -the name string is the same regardless of the extension.

Thanks for your help though. That was exactly what I needed.