Rendering curved line labels renders halos.
Placing a label onto a line prefers placing the label near a straight line segment that is long enough to fit it. If there are multiple such segments, the system uses the one closest to the center of the line.
Placing a label onto a line avoids placing the label onto a sequence of segments with high curvature, to improve legibility. The maximum bend angle is edited in the Style dialog, the default value is 60 degrees. Setting the maximum bend angle to 0 places labels near straight line segments only.
Labels with multiple lines of text, with a box, or with an icon are always placed only near points or near straight line segments.
Rendering labels with multiple lines of text supports reduced graphics mode.
Rendering labels with multiple lines of text uses the alignment specified in the Style dialog. Available choices are: left (default), center, right.
Coordinate systems that switched bases (5 cases) and coordinate transforms that switched source or target systems (3 cases) in the latest version of EPSG have been adjusted to coincide with their EPSG definitions.
The gray background area of the main window shows a dimmed Manifold logo and dimmed text with possible first actions for new users.
The context menu for a component in the Project pane includes the new Open command, which opens the component.
(Fix) Importing data automatically skips tables that cannot be accessed, eg, due to permissions. (This fixes the regression with MDB import in the previous build.)
(Fix) Opening a table that cannot be accessed, eg, due to permissions, no longer creates the fetch record in a table window.
(Fix) Double-clicking a word in a text window no longer sometimes fails to select it if the text has more than 64k characters.
(Fix) Nested include directives in queries resolve from the current data source instead of the data source of the topmost query. (This allows composing a query with includes, then including that query from a different data source with nested includes resolving correctly.)
(Fix) References to components in included queries resolve from the current data source instead of the data source of the topmost query. (This allows composing a query which references a script function, then including that query from a different data source with the script reference resolving correctly.)
Creating a primary key on an existing text field in PostgreSQL always uses the collation of the field. (This became a requirement in PostgreSQL 13. Secondary indexes continue to be able to use collations different from those of the fields.)
Creating an index on an existing text field in MySQL or SQL Server always uses the collation of the field and does not attempt to change it. (Previously, adding an index on a field that was not part of any other index was attempting to change the collation of the field to that specified for the index. We no longer do this and will instead show and likely edit the collation of a field directly in the UI.)
End of list.