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 help@sedris.org. If you are an associate, please use se-coders@sedris.org.
Return to: Top
- Library linking problem 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.
- Infinite loop condition in DCS_CompareString() and SE_CompareString() functions.
- Bug in Rules Checker when using global SE_Store.
- Limitation on the STF file name length to be less than 256.
- The content of the return 4x4 matrix is not initialized in SE_SetRotateMatrix4x4().
- 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() returning "false" even when there is a component of the given type present.
- SE_RemoveFromTransmittal() core dumps when removing a SE_DRM_CLS_IMAGE object.
- Fixed the DRM diagrams and general documentation.
- SE_GetComponent( ) function returning a component object after it has been removed from the aggregate.
- SE_HasComponent( ) function not behaving correctly when the "process inheritance" or "directly attached tables component" arguments are set to true.
- SE_GetReferencedTransmittalList( ) function not working properly and may crash the software.
- 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 causes 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 not crossing 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 consequently causing excessive memory allocation and slow down 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 incorrectly returning zero results.
- Unable to retrieve <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 failing 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
- The following SRM capabilities are not implemented:
- GCS coordinate validation.
- UTM coordinate validation.
- Horizontal datum transformations.
- The GC to LTP vector conversion doesn't work properly.
- The SE_GetErrorDescription( ) function is not fully implemented and it will, in most cases, return a null pointer (no error message).
- Once a GMI is placed in an environment with a specific SRF (the SRF of the <Environment Root> object), then it can no longer be consumed to a different SRF using the automatic conversion. If another SRF is needed for those objects, first the users have to extract the objects in their "native" SRF and then perform necessary conversions.
- The Rules Checker application in this release does not check all the DRM Constraints. Please read the Checker User's Guide for the list of constraints checked in this release. This application will be extended in subsequent releases to cover the remaining constraints.
- The read API's inheritance mechanism for <Colors> and <Rendering Properties> is incomplete. If an inherited <Color> or <Rendering Properties> object conflicts with a more "recent" object, the conflicting inherited object is completely overridden, rather than being deconflicted if possible. Consequently, the inherited information may be incomplete for these cases.
- The SE_EXACT_SEARCH option for search bounds is not implemented.
- An LSR <Model> can only be instanced into the following types of spatial reference frames:
- geodetic (2D or 3D),
- any projected spatial reference frame, e.g. Mercator,
- any augmented projected spatial reference frame, e.g. Augmented Mercator (3D),
- compatible LSR spatial reference frames
- The model_viewer application processes only polygonal <Primitive Geometry>; other primitives, e.g. <Lines> and <Points>, are currently ignored. Hence, a <Model> containing only a <Feature Model> without a <Geometry Model> will not be processed.
Return to: Top
Copyright © 2002 SEDRIS