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
The following fixes and changes were implemented for this release:
- General
- Fix a bug causing getRelationsCount() to return zero even when relations are actually present.
- Cleaner builds for many environments (elimination of warnings)
- Add support for Cygwin 1.6, Visual Studio 2008 and 2010
- In DRM
- None.
- In SRM
- See the SRM SDK's Release Notes for details.
- In EDCS
- See the EDCS SDK's Release Notes for details.
- In Transmittal Access C API
- None.
- In Transmittal Access C++ API
- Bug fix in getRelationsCount().
- In STF
- None.
- In applications
- Fix model_viewer crash when loading models with polygons that have an <Image Mapping Function> but for which the <Vertex> components don't specify <Texture Coordinate>s
- Rules_checker: the <<Image Mapping Functions and Texture Coordinates>> constraint more fully tests the case where <Image Mapping Function> instances are referenced via a <Property Set Index> rather than by direct attachment.
Return to: Top
- General
- Fixed RAIF inconsistency with handling conversion of units of measure when an SRF conversion was requested through the API.
- Removed references to STF_BlockOPT.cpp and STF_BlockOPT.hpp from the Visual C++ .NET project files.
- Direct attachment is now fully supported by the API when using a component iterator to resolve <Colour Index> instances.
- In DRM
- <Geometry Face>
- Clarified that an instance must have at least 3 associated <Geometry Edge> instances.
- Fixed the <Image> validation for THREE_MATERIALS <Image> instances to correctly enforce the requirements on the bits_of fields.
- Adjusted the The <<Quadrant Related Organizing Principle>> and <<Octant Related Organizing Principle>> constraints to align with the ISO specification, and the related validation of strict_organizing_principle for <Octant Related Features>, <Octant Related Geometry>, <Quadrant Related Features>, and <Quadrant Related Geometry> have been modified in accordance with the constraints.
- Fixes an error in the validation of <Variable> instances specified with SE_Variable_Code meanings.
- Updated SE_ConvertCoordinateToFields() so that all valid coordinate types are handled.
- Updated SE_ConvertFieldsToCoordinate() so that all valid concrete <Location> subclasses are handled.
- In SRM
- See the SRM SDK's Release Notes for details.
- In EDCS
- Added missing exported symbols for the EDCS library functions.
- See more fixes in EDCS Fixes and Limitations.
- Updated Visual C++ build environment files for dynamic compilation.
- In Transmittal Access C API
- Performance improvements when generating large transmittals.
- In Transmittal Access C++ API
- Performance improvements when opening transmittals with thousands of ITR references.
- In STF
- Fixed array freeing issue in URN resolution.
- Cygwin is now explicitly recognized on the list of little endian architectures.
- Fixed a bug when updating Data Table data after the transmittal is closed.
- Fixed a bug when writing integer field data.
- Fixed a memcpy overwrite during file access.
- In Applications
- Core applications have a more consistent style of reporting and usage. This includes specifying the implementation version of the SEDRIS SDK for which they were built.
- Syntax Checker now fully enforces the syntactic restrictions on aggregate/component relationships, including:
- Detecting malformed composition relationships that are 1-way instead of 2-way.
- Detecting a component that belongs to an incorrect number of aggregates. (e.g. a <Model> instance is a component of exactly one <Model Library>), including checking ITR relationships when all the relevant transmittals are accessible.
- Additional/improved tests for class field validation, e.g. required metadata fields.
- The rules_checker application now performs additional tests (for a fuller description of which constraints are tested, see P5V2 Checker User's Guide, section 2). The additional functionality includes more complete testing of:
- <<Presentation Domain Constraints>>
- <<Mandatory Metadata>>
- <<Image Anchor SRF>>
- <<Model SRF>>
- <<Environment Root SRF>>
- <<Polygon As Bounded Plane>>
- <<Property Characteristic Constraints>>
- various constraints related to feature topology and geometry topology
- various contraints related to <Volume Extent>.
- Rules_checker's handling of detecting co-located angular coordinate validation has been updated to prevent detection of false positives.
- For model_viewer, fixed an issue with handling <Animation Related Geometry> instances.
- For rules_checker, fixed an issue with testing for improper duplicate locations within geometry and topology for angular coordinate systems.
- The rules_checker application also performs additional tests (for a fuller description of which constraints are tested, see P5V2 Checker User's Guide, section 2). The additional functionality includes more complete testing of:
- <<Presentation Domain Constraints>>
- <<Property Characteristic Constraints>>
- various constraints related to feature topology and geometry topology
- ITR Test now produces a different transmittal as an example. The ITR relationships are now associations between <Geometry Model Instance> objects in transmittal A and <Geometry Model> objects in transmittals B and C (as opposed to the previously invalid <Model Library> to <Model> relationships). If the Depth application is passed a configuration file to run with "follow_model_instances" set to SE_TRUE, the relationships will be traversed and displayed.
Return to: Top
- Model Viewer Limitations.
- Rules Checker Limitations.
- One exception to ISO SEDRIS compliance is the use of WCHAR. This will be implemented in future releases.
- RAIF's capability of converting data between SRFs specified with different DSSs (for example, between the ellipsoid and MSL) is not fully supported. This will be addressed in future releases.
- Documentation for the SE_Character type references UTF-8 (Unicode), but the API currently does not handle UTF-8 characters (internally, SE_Character is currently implemented using char).
Return to: Top
Copyright © 2011 SEDRIS™