Changes for 9
The C runtime (CRT) is updated to 14.30.30704.0. (The portable ZIP published for the cutting edge build does not include the new version of the CRT, but the MSI / EXE packages for the next base build will. One of the notable changes in the new CRT is that the x64 flavor now includes native modules for the ARM64 architecture. You can download and install the new version of the CRT from Microsoft. You do not, however, have to do that right away and can wait for the next base build which will install it automatically. The current cutting edge build for 9 supports both the new version and the previous version of the CRT seamlessly.)
CUDA modules are recompiled using CUDA 11.5.1. This adds minor performance improvements.
The 'Side' edit in the Style dialog for numeric / vector values is renamed to 'Positive degrees' and is replaced with a combo box with choices for: '(none)', 'E', 'e', 'N', 'n', 'S', 's', 'W', 'w'.
Definitions for choice styles interpret 'value;' sequences as 'value=value;', that is, as a choice whose display name coincides with its value. This helps shorten the definitions for choice styles designed to simply limit values for a field to a specific subset without changing the way these values are displayed.
(Fix) The URL style for text values recognizes URLs with 'file:' and other non-web schemas.
The StringFormatAny query function supports choice styles for text values. The original text value is trimmed before matching any of the choices. The Style dialog for text values allows specifying a choice style.
Sample data in the Style dialog for vector values are adjusted to be simpler to read (were trying to illustrate too much).
Lists of choices in the Style dialogs have 'Value' and 'Show as' captions to make it clearer which column is doing what.
Editing a value formatted with a choice style sorts choices in the dropdown menu so that numbers appear before non-numbers and are sorted by a numeric, rather than text, value. A choice is treated as a number if it starts with a number. (Example order: '-9999 (invalid)', '1', '2', '2.5', '3 (standard)', '4', '10', 'other'.)
The About dialog reports Windows 11 as 'Windows 11 vvvv', Windows 10 as 'Windows 10 vvvv' and Windows Server 2016+ as 'Windows Server vvvv', with 'vvvv' being a Windows 10-type version label (eg, '21H1').
(Fix) Replacing a text fragment using a regular expression no longer fails to ignore case when matching class character sequences ('[a-c]' or '[abc]') if asked to ignore case.
The WEBP dataport is updated to use LIBWEBP 1.2.1. This fixes a couple of minor bugs in raster encoding.
The internal version of SQLITE used for all types of SQLITE data, including GPKG, is updated to 3.37.0. This adds support for STRICT tables, improves the performance of some types of queries, and fixes a couple of bugs.
The image server for Yandex Maps Street Map is hidden as discontinued (a new version seems to be coming).
(Fix) The LAS library dataport no longer sometimes returns incomplete results when working with more than ~500 files. (This was a series of issues occurring because the library was keeping too many files opened simultaneously for prolonged periods of time, hitting various limits itself and forcing other parts of the system into hitting these limits as well. We started by reworking the code to limit the number of files kept open at any given moment. Then we have been trying hard not to lose any performance when files above the limit had to be closed and reopened. In the end, thanks to a couple of algorithmic changes, instead of not losing too much performance, we managed to gain a little.)
(Fix) Computing a Voronoi diagram no longer sometimes fails to completely build shapes for some points in near-collinear point configurations (eg, a series of points following a reasonably smooth line in short steps).
(Fix) Exporting labels to DXF no longer fails if label text is defined using a text pattern.
(Fix) Exporting labels to KML no longer fails if label text is defined using a text pattern.
The KOBO dataport automatically refreshes opened tables every 5 minutes. This feature relies on table versions published by KOBO. Table versions do not advance for absolutely all types of changes to the underlying data, but they advance for the most common type of changes - adding new records - as well as for many of the less common types, such as adding or deleting fields.
End of list.