Subscribe to this thread
Home - Cutting Edge / All posts - Manifold System

7,643 post(s)
#12-Feb-18 17:47

SHA256: 7717e468bc12202d890393cdc2e7292b3a5ef72d6d290a83ee74136d9d9e1b46

SHA256: c14d26e1754c25a3f77962a565a2f2e11700084c0a03dda8c96e72f6657a111d


7,643 post(s)
#12-Feb-18 17:48


Entering coordinates for new drawing objects or labels in a map window no longer requires the selected tab in the Record pane to be Coordinates. Changing coordinates for existing objects still requires the selected tab to be Coordinates.

Holding Shift while Alt-clicking a drawing object or a label in a map window sets the selected tab in the Record pane to Coordinates instead of Values.

The Record pane for a label edits label text as a regular field value in the Values tab instead of using a separate text box in the Style tab. The record header for the field displays a distinctive icon.

Starting a new label or starting to edit an existing label automatically selects the value of the text field in the Values tab in the Record pane.

(Fix) Hiding a key field used for the selection in a table window no longer makes the table window unable to select or unselect records and unable to highlight selected records.

(Fix) Editing a cell value in a table window and ending editing by clicking a different cell no longer applies the editing to the clicked cell instead of the one that was being edited.

Migrating a labels component bound to a drawing from a MAP file created by Manifold 8 avoids creating extra computed fields to hold label text if the labels component was using a single field with no other text.

Migrating components from a MAP file created by Manifold 8 re-creates the folder structure.

Migrating components from a MAP file created by Manifold 8 migrates themes. The theme hierarchy is flattened with each theme converted into a drawing with formatting changes throughout the hierarchy captured.

Format pickers in the Style tab of the Record pane change the cursor to a 'hand' when the values they are displaying can be changed.

Pasting records between tables allows mapping fields using the new Paste dialog. By default, fields are mapped using their names and types. The default mapping for any field can be changed by editing it in the list (double-click or press F2).

The Paste dialog allows resetting changed fields back to the default mappings using the Autoselect Field command in the drop-down menu.

Pasting records into a table avoids displaying the Paste dialog if the system thinks it succeeded at mapping all fields possible. (The criteria: if the target table contains no fields that receive no data from the source table and can be set to receive data from one of the fields in the source table that has not yet been used, the system declares success.) Holding Shift while invoking the paste operation (Ctrl-Shift-V) forces the dialog to appear regardless of how successful the system thinks it has been at mapping fields.

Pasting records into a table in a MAP file avoids pasting data into the MFD_ID field by default. The user can still paste data into MFD_ID by selecting the source field for it.

Pasting records into a table stops at the first record that fails to paste instead of trying to paste as many records as possible. (The latter was a temporary measure used because we had no control over the paste operation.)

Pasting records into a table requires at least one matching field. If there are no matching fields, no records are pasted. (Previously the paste operation would create records with NULL values.)

The map window supports copying and pasting data for drawings and labels. Pasting records between drawings and labels automatically maps fields for geometry and / or text to each other.

Pasting records into a table / drawing / labels automatically converts coordinate systems for geometry fields. The conversion is performed only if both the target and source fields have a valid coordinate system (displayed in black instead of red in the coordinate system pickers, eg, in the Component pane).

Copying and pasting records reports the number of processed records in addition to the operation time.

The dataport for Enterprise storages supports themes.

The dataport for Enterprise storages supports folders. In addition, all virtual components exposed by an Enterprise storage are put into a special folder.

(Fix) The MIF dataport and several other dataports no longer fail to apply unit scale to easting and northing.

(Fix) The KML dataport puts created labels components into folders.

The KML dataport creates a map for all layers.

The KML dataport reads description and snippet values.

End of list.

Manifold User Community Use Agreement Copyright (C) 2007-2017 Manifold Software Limited. All rights reserved.