Fixes And Limitations

1. Introduction
2. Defects Fixed in This Release
3. Defects Fixed Since Release 3.0.3 Through Release 4.0
4. Known Defects and Limitations

Introduction

This document lists the bug fixes and known defects/limitations contained in this release.

For general information about this release, where to obtain it, and items that require specific attention, see the Release Notes.

For help, comments, and bug reports please send email to [email protected]. If you are an associate, please use [email protected].

Return to: Top

Defects Fixed in This Release

• Support has been added for the .Net compiler.
• Additional utility functions were provided to the SRM C++ API such as copy constructors.
• Miscellaneous SRM bug fixes related to:
  • polar_aspect,
  • retrieving orientation values,
  • TM conversion,
  • leaking of orientaton and direction,
  • inverted longitude and latitude in SRM_GetCoordValues(),
  • GD to GC conversion for spherical ORMs,
  • incorrect passing of ORM into internal functions
• Missing edcs3p1_to_edcs4p0.h include file
• Missing Data_Quality symbols
• SE_Address clone function and documentation
• Miscellaneous Rules Checker fixes related to:
  • spatial extent check for incompatible SRF,
  • incorrect constraint reference,
  • incorrect color index warning,
  • incorrect warning with Cross Reference DRM class
• SRM C sample app crash on Windows
• Memory leaks with:
  • SE_OpenTransmittal(),
  • SE_FreeClassificationParameters(),
  • SE_CloneHierarchyOrderParameters()
• Incorrect retrieval of data_count in SE_GetDataTableData()
• Depth handling of objects with ITR
• SE_DeleteAssociation bug causing unstable objects after associations were deleted
• Corrected mappings from EDCS 3.1 to 4.0
• SE_ValidHierarchyOrderParameters() incorrectly calling SE_ValidFields() for uninitialized items
• Directly attaching table components failing for component iterators

Return to: Top

Defects Fixed Since Release 3.0.3 Through Release 4.0

• The SE_CloneString( ) and EDCS_CloneString( ) functions fail to copy the "locale" field of the SE_String/EDCS_String when the string is the empty string.
• The SE_CompareStrings( ) and EDCS_CompareString( ) functions run into an infinity loop when comparing two identical strings.
• The 4x4 matrix in SE_SetRotateMatrix4x4( ) function may produce wrong results if the matrix is not properly initialized.
• The SE_GetImageData( ) function fails if called shortly after an Image has been created/modified.
• The SE_GetRearrangedImageData( ) function returns image upside-down or with texels shifted in unexpected directions (side-to-side, etc). This happens when the image scan direction is set to SE_IMG_SCAN_DIR_RIGHT_DOWN while the scanned image was originally stored with a scan direction of SE_IMG_SCAN_DIR_RIGHT_UP.
• The SE_GetElementOfDataTable( ) function may crash because of a misuse of stores.
• The SE_CloseTransmittal( ) function may crash when processing inheritance.
• When using search bounds on geodetic coordinates, false is returned even for objects which are inside the bounds.
• Default fields values are not completely initialized, which prevents comparison of default fields with an object's fields.
• Possible safety issues when using zlib version 1.1.3, upgraded to version 1.1.4.
• No vertical and horizontal datum shift support for SRM conversions (see remaining limitations below).
• The Depth application does not include association link objects in its object counts.
• In some cases a library linking problem may arise due to missing exported symbols.
• Malformed macro definitions for SE_ClassCount( ) and SE_TypeCount( ) functions.
• Bug in label search EDCS_LabelToEECode( ) and EDCS_LabelToEGCode( ) functions.
• Rules Checker incorrectly using a global SE_Store.
• Limitation on the STF file name length to be less than 256.
• In SRM_Matrix3x3Multiply( ) and SRM_Matrix4x4Multiply( ), the result of the operation is incorrect when one of the input matrices memory space is the same as the output matrix.
• Depth -vv option not printing out the data table values for data tables with only 1 axis and only 1 table property description.
• SE_HasComponents( ) may return "false" even when there is a component of the given type present.
• SE_RemoveFromTransmittal( ) may fail when removing a SE_DRM_CLS_IMAGE object.
• DRM diagrams and general documentation updates and fixes.
• SE_GetComponent( ) function returning a component object after it has been removed from the aggregate.
• SE_HasComponent( ) function may not behave correctly when the "process inheritance" or "directly attach table components" arguments are set to true.
• SE_GetReferencedTransmittalList( ) function may not work properly.
• Fixed SE_GetPublishedLabels( ) function to just return the label(s) under which the object is published and to allow an object to be published multiple times.
• Rules Checker not being able to process <Base Perimeter Data>, <Base Time Data> and <Separating Planes> classes.
• Using SE_OpenTransmittalByFile function opening a transmittal in update mode multiple times may cause user editing changes to be lost.
• Microsoft compiler unable to handle the fields in <Base Reference Vector> correctly due to its particular type casting mechanism.
• Search bounds did not cross ITR boundaries to retrieve objects.
• In processing large transmittals, i.e. the ones that have large amount of relationships among objects, internal block caching was not processed properly and may cause excessive memory allocation and slow downs in execution.
• SE_GetNumberOfPathsToTransmittalRoot( ) function incorrectly calculating the value for <Feature Node> instances bound to looped <Feature Edge> instances.
• Search filtering using the SE_COMPONENT_TYPE_MATCH search rule may incorrectly return zero results.
• Issues when retrieving <Data Table> data when <Data Table> has a set of identical elements.
• SE_ResolveTransmittalName( ) function incorrectly using an SE_Store, causing invalid names to be returned on subsequent calls.
• SE_RemoveComponentRelationship( ) function may fail to remove relationships with link objects.
• Default options for the depth application were set incorrectly to true for the "process inheritance" and "directly attach table components" parameters.
• Altitude conversions incorrectly calculated for Geodetic (GD) SRF.
• GD <=> UTM conversions returning improper extended range warnings and incorrect longitudes.
• Problem with LTP conversions producing wrong results due to sine/cosine mix up.

Return to: Top

Known Defects and Limitations

• Model Viewer's Limitations
• Depth, Rules Checker, and Syntax Checker Limitations
• Removing a SE_DRM_CLS_DATA_TABLE object will result in the cell data not being removed from the file. The cell data will not be accessible, but the file size will not be reduced.
• The following SRF Templates are not supported in this release: Local Space Azimuthal, Local Space Polar, Polar Stereographic, Equidistance Cylindrical, and Oblique Mercator
• The SRM calculation capability supported in this release are: coordinate conversion, direction conversion, orientation conversion, natural region calculation, and Euclidean distance calculation. The remaining calculation capability will be supported in subsequent releases.

Return to: Top

Copyright © 2005 SEDRIS™