Invoking Help - Documentation opens the user manual instead of the page that contains a link to it.
Pressing F1 in a comment or script window opens the keyboard reference for that window.
Queries representing database views report their schemas. The Project pane allows viewing the schema of such a query by right-clicking it and selecting the Schema command.
Queries for the Manifold query engine report their schemas as long as the schema of the result table can be discovered without running the query. (Example 1: SELECT * FROM t WHERE ...; - the schema of the result table can be discovered without running the query. Example 2: CREATE TABLE t (...); SELECT * FROM t; - the schema of the result table cannot be discovered without running the query.)
The New Drawing dialog allows creating a new component based on a query, as long as the query can report its schema.
The New Image dialog allows creating a new component based on a query, as long as the query can report its schema.
(Fix) The New Labels dialog correctly handles creating a new component based on a drawing based on a query.
The New Drawing and New Image dialogs disallow adding spatial indexes to tables which do not support altering table schema (eg, read-only).
The New Drawing and New Image dialogs no longer list system tables (MFD_xxx).
Creating a new component on a data source which adjusts names of created components (commonly seen with databases which prepend schema name) captures the final created name and correctly selects the created component in the Project pane.
(Fix) Dropping a query into the query builder no longer runs it to determine the schema of the result table. (This was a misfeature.)
The DB2 dataport reports schemas for materialized views.
The Oracle dataport treats materialized views as queries, not as tables.
The PostgreSQL dataport allows accessing materialized views and reports their schemas.
The SQL Server dataport tries to resolve the SRID of geometry values in a table to the system MFD_SRID table (composed based on a SQL Server view). If the SRID cannot be resolved, it is interpreted as an EPSG code, according to the Microsoft guidelines and similar to how these codes are used in practice by Manifold 8 and other products.
Dataports for SQL Server and other databases map unrecognized field types to NVARCHAR. (This allows working with partial data in tables that contain fields which the database driver cannot work with - usually due to a bug, a misconfiguration, or a version skew.)
(Fix) Reading a CTG file no longer sometimes creates an incomplete coordinate system.
(Fix) Reading a MIF file no longer sometimes creates a wrong coordinate system.
Exporting vector data to DXF, GDB, MFD, MIF files (in addition to E00 and SHP which were done earlier) clears the values of the local offset and local shift values in the exported coordinate system and forces the axis order to XY.
Linking an isolated GCDB DAT file for a single state no longer creates the 'API' comments component with the list of supported geocoding functions (because geocoding functions require linking the full GCDB data set, not a single file).
Sorting records in a table window requires Ctrl-clicking the field header instead of just clicking. Shift-clicking the field header continues to add the field to the current sort order.
Rendering a label bound to an area tries to places the label into the middle of the visible portion of the area.
The advanced rendering engine supports rendering labels with shadows. The basic rendering engine scales label shadows during printing (were frequently invisible before).
The advanced rendering engine supports rendering labels with halos. The basic rendering engine scales label halos during printing (were frequently invisible before).
The advanced rendering engine supports strikeout and underline font options.
End of list.