Gnats 5912: Inserting columns in table slots with different units messes up the units on the existing columns.
Fixed for RiverWare 7.0.6, 3-08-2017.

Actually, three problems related to changing the number of columns in TableSlots were found and fixed:

1. Column Insertion in TableSlot (as described in the bug report) -- Column Units Problem.
2. Column Deletion in TableSlot -- Column Units Problem.
3. Column Deletion in TableSlot with Column Map (e.g. Periodic Slot) -- Column Value Problem.

These problems, and their fixes, are illustrated in the following three sections. (The first two sections each have two distinct examples).

(1) Column Insertion in TableSlot -- Column Units Problem.

Method TableSlot::insertColumn (int) wasn't adjusting column units starting at the new column.

(2) Column Deletion in TableSlot -- Column Units Problem.

Deleting a column from a table slot also wasn't adjusting column units.  See changes in TableSlot::deleteColumn (int).

(3) Column Deletion in TableSlot with Column Map (e.g. Periodic Slot) -- Column Value Problem.

Deleting a column from a TableSlot (e.g. a Periodic Slot) having a "column map" (NumericDimension) had been just truncating the column map instead of removing the deleted column's item from the column map.  See changes in TableSlot::deleteColumn (int) and TableSlot::deleteLastColumn().

--- (end) ---