The log window tracks attempts to load add-ins from DLL files.
Loading add-ins ignores DLL files without an accompanying .DLL.ADDIN file (the contents may currently be empty). (This dramatically reduces the time to initialize the main menu on configurations with lots of DLL modules in ~\bin, ~\bin64 and ~\shared which do not include add-ins, such as DLLs for database clients or scripting engines.)
Saving the current location from a map window saves the name of the context component into the location. Right-clicking a location with a context component in the Project pane allows opening the context component and then navigating to the location using the new View command.
Creating a new location based on a window using the New Location dialog saves the name of the context component into the location as long as it is reachable from the data source of the location.
Opening MAP files created by 8 migrates component views into locations. The created locations are put into the same folder as the producing component.
The log window reports the location of the active log file on startup.
The tracker tool reports total length using units of the current coordinate system as long as it is not lat/lon.
The tracker tool reduces reported values for bearing and length to three decimal digits. The 'L:' and 'B:' captions are removed.
Right-clicking the map window with the tracker tool active displays the context menu which allows copying the values for bearing and length (both values are copied with full precision).
The Select and Transform panes specify parameter values which can be set to fields using a new parameter picker control. The control allows switching between fields of the required type, and includes options to use value or expression. Text entered for value is automatically quoted according to the value type (there is no need to type '...' for string values, no need to prefix each backslash with another backslash, etc). Text entered for expression is left intact (can freely combine field names, literals, etc, as before).
The PostgreSQL dataport optimizes bulk inserts, deletes and updates.
The GPKG dataport optimizes bulk inserts.
Exporting vector data to GPKG adds spatial indexes after writing geometry, for performance.
(Fix) The ODBC driver no longer sometimes fails to return data for an external data source accessed through the data source component in a MAP file.
Parsing coordinate systems from WKT (PRJ) better handles Winkel-Tripel, polar stereographic and multiple other system types.
Parsing coordinate systems from WKT (PRJ) recognizes coordinate axes.
The DWG dataport recognizes variants of DWG up to R2018 and can read quite a bit more data out of modern variants.
The DWG dataport maps character data to Unicode using codepage data in the file.
(Fix) Accessing a GPKG drawing built on a table without an rtree index no longer generates an error.
End of list.