frontend, libobs, plugins: Natural sorting for files, profile and scene names

[Dankirk]

Description

Applies natural, locale aware sorting when drag&dropping many sources at once and to profile and scene names in menus. For slideshow (mk2) and VLC the files in added directories are cycled using this sorting method instead of an arbitrary order. The order of items in the slideshow listbox is otherwise preserved.

For background: Natural sort means sorting by numerical value. Alphabetical sort arranges numbers like this: 1 < 10 < 11 < 2 < 3.
Natural sort does it this way: 1 < 2 < 3 < 10 < 11.
The natural sort is what Windows explorer uses under the hood when you sort by name or use ls -v on unix.

For general use, qt-wrappers has couple new methods for natural sorting:

template<typename T, typename Callback> void NaturalSort(QList<T> &list, Callback extractor, bool reverse = false)
template<typename T> void NaturalSort(QList<T> &list, bool reverse = false)

The list parameter is sorted using locale and number value aware algorithm with QCollator. It works with QString and QStringView. System locale is used to achieve the locale-aware sorting.

For lower level stuff in C, like slideshow plugin, there's new comparison functions for char* and wchar_t* in dstr library.

EXPORT int astrnatcmp(const char *str1, const char *str2);
EXPORT int wstrnatcmp(const wchar_t *str1, const wchar_t *str2);

The return value is <0, 0 or >0 as expected for return value of qsort()'s callback function. This sorting uses strcoll() and wcscoll() respectively for locale aware sorting, but does natural number sorting using a custom implementation. The locale aware sorting, however, is currently with limited use on Windows, as the program is using the process wide 'C' locale. Changing this behavior is out of this PR scope, so I made another here #12624.

OBSBasic_Dropfiles.cpp has somewhat sizable changes, due to how late the names for listed sources were acquired. This changes it so names are gathered first for sorting and only later added to the UI.

Motivation and Context

Fixes #10382
Couple requests on forums here and here. Most recently I saw a Youtuber mention this during a live stream.

The issue is with filenames and other listings that contain incremental numbers which are not sorted intuitively when sorted alphabetically. In fact the alphabetical sorting is also coincidental, since the methods for iterating over files give no guarantee about the order.

How Has This Been Tested?

I tested the features with files in directories with the following file names to see if they are sorted correctly:
testnames.txt
The files should appear in the order listed for en_FI locale. The files with 'ä' or 'ö' could be in another place for different locales. The important part is the numerical comparison works, so 5.jpg is before 10.jpg while the opposite is true for basic alphabetical sorting.

I'm on Windows 11 English US version, but with Finnish region/locale settings.

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[Dankirk]

Updated the list of filenames I tested the sorting with and I'm happy with the results.

One issue remains:
For image slideshow directories, the sorting is not locale aware (natural sort works), because the app uses the default 'C' locale. The app does call QLocale::setDefault() for Qt based things during app start, but does not call setlocale() for lower level functions. For sorting purposes setting LC_COLLATE with setlocale() would suffice, but it is uncertain how much that affects other things. Parts that can use qt-wrapper, use QCollator instead with system locale. For plain C I can't seem to find any multithreading safe ways to use different locale temporarily.

There is also a question if the default locale set with QLocale should actually be the system locale instead of the app language/translations locale? If so, could we then also do so with setlocale() to match?
This is a bit out of this PR scope though.

[Warchamp7]

Approving on a conceptual/UX level, but others will need to speak to the technical implications