The Layers pane allows grouping layers for maps, frames for layouts, and fields for tables.
Each layer group has a leading layer, layers following it can be grouped with it using the Group button in the toolbar. Grouping indents child layers one step to the right. Groups can be nested. Ungrouping is done using the Ungroup button in the toolbar. Selecting a leading layer in a group selects all layers in that group, including layers in nested groups. This then allows quickly turning on / off, etc, the entire group. Adding, removing, reordering layers auto-adjusts groups.
The Layers pane supports the following shortcuts: Ctrl-Right = Group, Ctrl-Left = Ungroup.
(In the current build, layer groups only appear in the Layers pane. Future builds will allow using layer groups from component windows as well.)
Code for ECW / JPEG2000 is moved into a separate DLL and is not loaded until it is needed.
Code for external Unicode collates is moved into a separate DLL and is not loaded until it is needed.
Data for external Unicode collates is loaded from a single shared location (~\shared\icudtl.dat) in both 32-bit and 64-bit modes.
Code for V8 is moved into a separate DLL and is not loaded until it is needed.
Viewer installs exclude the majority of code for V8 (which we do not need because Viewer disallows running scripts).
(The changes above decrease the size of installs and conserve resources at runtime. More importantly, they significantly decrease the startup time, usually cutting it in half or so, which is very noticeable.)
Installation packages register the ODBC driver without running code in Manifold binaries. (This helps solve the most popular problem with uninstalls - that of the 32-bit executable blocked due to a false positive in a third-party antivirus tool and thus not being able to run as part of the uninstall.)
The Help - About dialog shows the install state of the ODBC driver (32-bit or 64-bit, regular or cutting edge). Possible report types:
- 'Not installed' - the ODBC driver is not installed
- 'Installed' - the ODBC driver is installed into the current location from which the application has been launched
- 'Installed with mismatching options' - the ODBC driver is installed into the current location, but the install is either partial or damaged or out-of-date, the driver has to be reinstalled to work properly
- 'Installed in different location' - the ODBC driver is installed but into a different location (eg, portable install in a different folder),
The dialog for Viewer does not show the install state of the ODBC driver, because Viewer does not include the ODBC driver.
The Help - About dialog allows installing (repairing) or uninstalling the ODBC driver from within the dialog, as long as the user has administrative privileges. Command-line options to install or uninstall the ODBC driver are no longer supported.
GPGPU code requires CUDA devices of compute capability 3.0+ (Kepler or higher, cards with Kepler started appearing in 2012). All GPGPU modules have been adjusted to use Kepler features.
GPGPU code can use much more memory, allowing for bigger tiles / longer sequences of operations (not specific to the new requirement for Kepler or higher).
All types of Kriging - regular / median Polish / regression - compute model parameters on GPGPU, if available. (This is significantly faster than doing the same on CPU.)
The schema field dialog shows and allows specifying type restrictions for geometry fields (area / line / point) for databases that support it.
The schema field dialog hides bounds and Z option for geometry fields that are not native to the database (GEOMMFD and GEOMWKB, both stored as binary data opaque to the database).
The schema index dialog disallows creating spatial indexes on geometry fields that are not native to the database.
Linking ECW / JPEG2K / SID allow editing the coordinate system, style and other metadata for the linked images.
Exporting an image to PNG or WEBP produces color (with or without alpha), grayscale or palette data depending on style info.
Exporting a big image to ERDAS IMG or TIFF skips producing data for intermediate level 1 (produces intermediate levels starting from level 2) to save space.
Reading GML, GeoJSON, KML and similar data preserves all coordinates in multi-type geometry values. Geometry values declared as multi-type but with all parts having the same underlying type (all areas, all lines, or all points) preserve that type. Geometry values that mix parts of different types are converted to either areas (if there are no lines and the value is a mix of areas and point) or lines (all other cases).
End of list.