custom units not inserted into data package
Used the custom unit dialog and examined the resulting data package xml. Custom
unit (incorrectly) inserted as a standard unit and custom info not inserted in
the data package xml.
#2 Updated by Dan Higgins over 18 years ago
If one immediately (after opening Morpho) edits column metadata in an existing
table and changes to a custom unit, everything seems to work OK. HOwever, if one
creates a new datatable, then the customUnit gets entered as a standardUnit, and
then editing a column also no longer seems to work correctly!
#3 Updated by Perumal Sambasivam over 18 years ago
this bug seems to be fixed. The problem was due to the wizard creating a
temporary DOM and treating that as the current data package. Hence all changes
to that DOM were not reflected in the original package. Modified the code so
that the additional metadata is now added to the original DOM. It works fine
now. I will close the bug after complete testing.
#4 Updated by Dan Higgins over 18 years ago
The basic bug does seem to be fixed (i.e. custom unit info is added to the
datapackage, creating a valid eml doc)
There is one issue in window order. When one brings up the custom unit dialog,
the TextImportWizard window is moved behind the DataPackage window, so that when
the custom unit dialog is closed, the DataPackage hides the TextImport WIndow,
which may be a problem when working in the Wizard.