The Layers pane allows showing and editing scale limits (zoom ranges) for map layers using the new commands: Show Farthest (Max) Scale / Show Closest (Min) Scale. The map window honors layer scale limits: layers whose limits do not include the current window scale are hidden and do not participate in interactive operations -- editing / picking / selecting / snapping.
(The layout window does not currently honor layer scale limits neither on screen nor during printing. Both these things are coming in the next build.)
The Layers pane shortens the display of max / min scales for map layers to: 1:xx / 1:xxk / 1:xxm / 1:xxb -- and then 1:xxe+xx for very large values -- for readability.
Exporting data to a GDB automatically truncates text values to the maximum allowed length.
(Regarding limits on the size of text values. In Manifold 9, the maximum size of text values is 2 GB. This is a pretty big value that is nearly never reached in practice. Many other data sources, however, have much stricter limits, so there is a question of what to do when we have to write text values to such a data source and some of the values are over the limit. After discussions, we settled on the following rules: (a) attempting to set an overly long value during an interactive edit should fail and complain that the value is too long, (b) attempting to set an overly long value using INSERT or UPDATE in a query, or their equivalents in a script should also fail and complain that the value is too long, however, (c) attempting to export data with one or more values above the limit should not fail and should automatically truncate the values to the maximum allowed length. The rationale for export behaving differently from other writes is that if we make the export also fail and complain, the very next steps performed by the user will quite likely be reducing the length of text values *in the original data* just so that they are under the limit imposed by the data source they want to export to. It feels much better to just let the export trim text values as needed as they are being written, while keeping the original data intact.)
Exporting data to a GDB that resulted in the truncation of text values reports the names of fields containing truncated values as well as the total number of truncated values in the log.
Exporting data to a SHP automatically truncates text values to the maximum allowed length and reports truncations in the log.
Exporting data to a DBF automatically truncates text values to the maximum allowed length and reports truncations in the log.
Exporting data to a KML / KMZ exports values of fields for drawing records as allowed by KML 2.2. Binary fields (geoms / tiles / varbinary) are not exported. Name / Description fields are no longer special-cased and are exported as regular fields.
Exporting data to a KML / KMZ exports labels bound to an area as bound to a point located in the inner centroid of the area, labels bound to a line as bound to a point in the middle of the line (half-length through the line), and labels bound to a multipoint as bound to the first point of the multipoint, to let Google products show such labels.
Reading data from a KML / KMZ reads field values.
End of list.