Documentation update

CHANGELOG.md

@@ -6,14 +6,17 @@
 
 ### Release overview
 
-2.2 maintenance release.
+2.2 maintenance release. This fixes some bugs and implements a new look for the Modern theme by adding a new set of carousel icons.
+
+Some improvements were also made to the systems sorting functionality.
 
 ### Detailed list of changes
 
+* Added new carousel icons and two new variants to the Modern theme
+* Added system carousel fastScrolling to the Modern theme
 * Added secondary sorting by fullname when sorting systems
 * The Orphaned data cleanup utility will now skip any system where a flatten.txt file is present
 * Changed a number of error messages in the Orphaned data cleanup utility from uppercase to lowercase
-* (modern-es-de) Added system carousel fastScrolling
 * The application release number is now tracked on startup instead of the application version
 * Changed the systems sorting platform from "Peripheral" to "Console" for the fds, megacd, megacdjp, n64dd, pcenginecd and satellaview systems
 * Changed the systems sorting platform from "Peripheral" to "Console" for the sega32x, sega32xjp, sega32xna, segacd, sgb, sufami and tg-cd systems
@@ -26,6 +29,7 @@
 * Horizontally scrolling text containers sometimes had an incorrect vertical offset
 * The year was incorrect in the systems sorting files for the amiga1200, amiga600, astrocde, coco, kodi, solarus, stv and trs-80 systems
 * The fmtowns system was incorrectly classified as a console and with the wrong release year in the systems sorting files
+* Fixed a small memory leak in the application updater
 
 ## Version 2.2.0
 

INSTALL.md

@@ -1176,7 +1176,7 @@ If you're using the AppImage release of ES-DE then the bundled es_systems.xml fi
 
 It doesn't matter in which order you define the systems as they will be sorted by the `<fullname>` tag or by the optional `<systemsortname>` tag when displayed inside the application. But it's still a good idea to add the systems in alphabetical order to make the configuration file easier to maintain.
 
-Note that the `<systemsortname>` tags are sorted in [lexicographic order](https://en.wikipedia.org/wiki/Lexicographic_order) so 11 will be sorted above 2 but 002 will be sorted above 011.
+Note that the `<systemsortname>` tags are sorted in [lexicographic order](https://en.wikipedia.org/wiki/Lexicographic_order) so 11 will be sorted above 2 but 002 will be sorted above 011. Secondary sorting will always be done by the fullname tag in es_systems.xml.
 
 But instead of changing the sorting directly in the es_systems.xml file it could be a better idea to use the dedicated es_systems_sorting.xml file instead. How to do that is described later in this document.
 

USERGUIDE.md

@@ -357,6 +357,8 @@ In order to remove such unnecessary media files and configuration file entries,
 
 It's recommended to run this utility with the _Show hidden games_ setting enabled as orphaned gamelist.xml folder entries may otherwise not get purged.
 
+If a system has a flatten.txt file present in the root of its directory, then the system will be completely skipped and an error will be logged (using folder flattening is strongly discouraged in general).
+
 Note that there are no guarantees that any processed gamelist.xml files will be usable in any other applications than ES-DE. An attempt is made to retain the file structure but data unknown to ES-DE may get purged during cleanup.
 
 If the utility finds any data to be removed, a backup of the old files will be made. This will end up in a `CLEANUP` directory and will contain a date and time stamp. For example:
@@ -1021,6 +1023,7 @@ However, some users have a setup where they have separated games inside their sy
 * Any identically named files will be added only once in a semi-random fashion, meaning you could miss some games
 * If there is metadata available for multiple games with the same filename (which could happen if scraping was done prior to flattening the folders) then the behavior is undefined and metadata from the wrong game may get used
 * Some systems like MS-DOS and ScummVM may be completely broken
+* The Orphaned data cleanup utility will not process the system
 * The setup may cause confusion when reorganizing your collection and similar because what you'll see inside ES-DE will not reflect what you see when navigating the ROM directory in your operating system's file manager
 
 Only enable this functionality if you know exactly what you're doing and understand the adverse side effects mentioned above. If you have any name collisions in your directory structure then make sure to rename each file to have a unique name. Also delete your gamelist.xml file and rescrape the entire system after fixing any collisions as it's otherwise random which metadata will be used for those games.