Sort order of Resource Manager doesn't match system

[thetasig]

I'm not sure why this is the case, but if you compare, say, the Mac Finder list of resources (photos, in my case) with Lightroom's list of photos and with Affinity Publisher's List of the Resource Manager, the sort order of the Mac and LR match, but the Resource Manager has a different order.

I'm not totally sure, but it seems to be the way leading numbers on the names are sorted. Mac and LR sort by the numeric value, then alphabetical, Publisher sorts by, I believe, hex value - or by character value, then alphabetical characters. Thus, "007" comes before "6" in Publisher, whereas it's the reverse on the Mac and in LR.

This plays havoc with the user's ability to cross-check and validate Publisher resources against system lists.

Can't we have a match of Publisher's sort (everywhere, e.g., Resource Manager, Index, etc.) with the system it's installed on? Thanks!

See example screenshot.

 

[walt.farrell]

Mac Finder and LR are doing a numeric sort, and Affinity Resource Manager is doing an alphabetic sort.

Alphabetically, 0 < 6, so 007 sorts before 6. But considered numerically, 007 = 7, and 6 < 7, so 6-photo comes before 007-photo.

[thetasig]

Thanks, Walt.

Yes, seems that is the case.

I still would love to have my applications match up with the system defaults in that regard. As it is, I can't really change any of them, especially the Resource Manager and Lightroom. Yes, it is possible, though tedious, to capture the system list and then put it into some other application that can sort alphabetically, but having to do that many times over can really eat up a lot of time. The Affinity User Interface should do that by default (system-dependent) IMHO.

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.