(We have changes for layer groups coming in the next build. We are going with folders instead of leading layers, to have the same concept of folders apply everywhere where we have hierarchy.)
Clicking a toggle icon for a layer in the Layers pane toggles the layer (and all selected layers if the clicked layer is selected) on and off.
Updating image style from the Style pane accepts changes made both to image palette / channel map and to shading. Shading controls are enabled even if the image is rendered using a channel map with shading not applied.
Switching cursor mode in a layout window clears active layout frames.
Alt-click, Alt-drag, Ctrl-click, Ctrl-drag reset cursor mode in layout window. (Inserting a new layout frame and then Alt-clicking an existing frame will activate the existing frame instead of inserting one more new frame. Same for Ctrl-clicking and Ctrl-dragging which will start selecting frames.)
Alt-click, Alt-drag, Ctrl-click, Ctrl-drag reset cursor mode in map window. (The behavior is the same as for layout frames. In addition, Alt-clicking a record in drawing / image / labels, then Alt-clicking a different record will put the new record into the Record pane. Same for Ctrl-clicking and Ctrl-dragging which will clear the Record pane and start selecting records.)
(Fix) Dragging the first coordinate of an area branch in a map window no longer fails to move the matching last coordinate of the branch.
Dragging coordinates of geometry values in a map window only allows dragging the focused coordinate. To drag a coordinate other than focused, first click it to make it focused. (This protects from accidental drags and makes drags more predictable.)
Painting coordinates of an edited geometry value in a map window always puts the focused coordinate on top of all other coordinates.
Painting an outline of a geometry value in a map window uses halo for line / area outline, thick border and halo for the focused coordinate.
Painting an outline of a geometry value in a map window paints a box around the whole value if it is too small at the current zoom, to make it more visible. The additional box is only painted for existing records when the coordinates are not being edited (the Coordinates tab in the Record pane is not active).
Painting a snap reticule in a map window uses halo.
The Record pane disables moving to the previous / next record if it is editing a new object.
Moving to the previous / next record in a layout or map window from the Record pane pans / zooms the window to the new record. If the record is already completely visible (although possibly small), the view is not altered. If the record is small enough to fit into the window at current scale, the window is panned to include the record. If the record is too big to fit into the window at current scale, the window is zoomed to the record.
Alt-clicking in a drawing / labels layer in a map window picks up to 10 records under the clicked location. The first picked record is put into the Record pane, other picked records can be moved to using Move to Next. (That is, if there are multiple picked records, the virtual record order used by the Record pane is altered to put the picked records first and unpicked records next.)
Moving to the previous / next record in a map window from the Record pane uses a background thread to (show the progress dialog and) allow canceling the move if it takes too long. (This is useful for slow data sources and for components made on queries.)
The Record pane allows moving only to selected records using a toolbar button. (Turning the mode on keeps the current record unchanged, but moving to the previous / next record will only move to selected records. If there are no selected records in the specified direction, the current record stays unchanged.)
The Record pane shows and allows editing pixel values in tiles. Pixel values are shown as X - Y - value (possibly multi-channel) - toggle that indicates whether the pixel is present or missing. Pixel values can be selected, values can be edited and toggled, editing or toggling a selected pixel value alters all selected pixel values. Changed pixel values are highlighted. (Saving changes to the edited tile will currently require updating intermediate levels manually in the map window - we will perhaps automatically update them if they were updated before the changes.)
The Record pane shows field names in the list of field values as readonly.
(Fix) Writing multi-point geometry values with multiple branches to SQL Server no longer fails.
Composing contours for many heights (thousands+) performs much faster.
Composing traces for many values (thousands+) performs much faster. The limit onto the number of unique values is removed.
New query functions:
- TileWatershedAreasSinks / TileWatershedAreasSinksPar - takes an image, returns watershed areas for all sinks (no minimum flow parameter necessary). TileWatershedAreasSinksPar is a parallel variant, takes thread configuration as an extra parameter.
- TileWatershedAreasUpstream / TileWatershedAreasUpstreamPar - takes an image and a drawing of points, returns upstream watershed areas for each point. TileWatershedAreasUpstream is a parallel variant, takes thread configuration as an extra parameter.
- TileWatershedAreaUpstream / TileWatershedAreaUpstreamPar - takes an image and a coordinate, returns upstream watershed area for the coordinate. TileWatershedAreaUpstreamPar is a parallel variant, takes thread configuration as an extra parameter.
- TileWatershedLinesUpstream / TileWatershedLinesUpstreamPar - takes an image, a drawing of points and the minimum flow value, returns upstream watershed lines for each point. TileWatershedLinesUpstreamPar is a parallel variant, takes thread configuration as an extra parameter.
- TileWatershedLineUpstream / TileWatershedLineUpstreamPar - takes an image, a coordinate and the minimum flow value, returns upstream watershed line for the coordinate. TileWatershedLineUpstreamPar is a parallel variant, takes thread configuration as an extra parameter.
New transform: Watershed Area, Sinks - computes watershed areas for all sinks.
(Fix) Parsing a coordinate system from WKT (PRJ) no longer sometimes erroneously returns a system that uses YX axes.
(Fix) Exporting a TIFF or ERDAS IMG no longer sometimes fails when writing data for intermediate levels.
Exporting a TIFF or ERDAS IMG skips writing data for intermediate levels if the image is too big (intermediate levels will strain the disk) or too small (intermediate levels are unnecessary, easy to compute on the fly).
There is a new dataport for web CSV, similar to web GeoJSON, to allow easy linking of web URLs with CSV data.
The Options dialog allows specifying a value for the cache size. The default is '(auto)' and that can be overriden with an explicit value in GBs. The minimum allowed value is 4 GB (which is the default) and the maximum allowed value is 64 GB, however the dialog only lists values up to the installed physical memory. The option only applies to 64-bit mode, the 32-bit mode ignores it. Any changes to the cache size are only applied after restarting the application. (This allows increasing the cache size in the 64-bit mode, which could help performance of some operations. Increasing the cache size can also hurt performance depending on the scenario. Generally, it makes sense to keep the cache size no bigger than half of the installed physical memory, perhaps slightly lower than that if you are regularly running multiple instances of Manifold. Whenever in doubt about the effect on performance, use '(auto)', this is conservative and safe.)
End of list.