------------------------------------------------------------ Release Notes for SDK (7.0.0.2167) 5/28/2008 1. *** API CHANGE *** As described in the Porting Guide section of the User Manual, breaking changes have been introduced to the API, in order to address the needs of more flexible workflows and pipelines in applications. This will require small changes to existing code. 2. The LTIOFileStream class now support +2GB files. The LTIOFileStream64 class has been removed. 3. The mix of supported platforms has been updated. See platforms.txt for details. 4. A number of bugs have been fixed in the JP2 and NITF readers and writers. 5. Small performance improvements have been made in many areas of the code. 6. Member functions that are not documented (or are explicitly marked as LizardTech-only) should in general not be used by third-party developers. ------------------------------------------------------------ Release Notes for SDK (6.0.7.1407) 6/22/2006 Note: The Solaris gcc platforms, and the Linux gcc2.95 platform have been discontinued with this release. ------------------------------------------------------------ Release Notes for SDK (5.0.6.947br955) 5/2/2005 Note: The Solaris x86 platform has been discontinued as a supported platform with this release. ------------------------------------------------------------ Release Notes for SDK (4.0.10.720) 12/9/2004 1. TIFFImageWriter will not work correctly if the output target is a stream (as opposed to a file). A workaround is to write the output to a temporary file, then load that file into a stream. This issue will be fixed in a subsequent release. [9715] 2. The following JP2ImageReader code fragment will return an error code (50916) from the initialize() call: const char* fileName = ... J2KImageReader reader(LTFileSpec(fileName)); LT_STATUS sts = reader.initialize(); The workaround is to not inline the LTFileSpec construction, as follows: const char* fileName = ... LTFileSpec fileSpec(fileName); J2KImageReader reader(fileSpec); LT_STATUS sts = reader.initialize(); This issue will be fixed in a subsequent release. [10042