openexr-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Openexr-user] OpenEXR 1.6.0 and CTL 1.4.0 released


From: Florian Kainz
Subject: Re: [Openexr-user] OpenEXR 1.6.0 and CTL 1.4.0 released
Date: Wed, 22 Aug 2007 09:58:03 -0700
User-agent: Mozilla Thunderbird 1.0 (X11/20041207)

This particular change was intended to fix a naming inconsistency in
ImfStandardAttributes.h.  I was under the impression that few, if any,
people cared about the utcOffset attribute.  Next time I'll be more
careful.

By the way, the change in ImfStandardAttributes.h affects only the
name of two functions (addUtcOffset and hasUtcOffset); the file format
has not changed.

Florian


Brad Hards wrote:
On Saturday 04 August 2007 13:14, Florian Kainz wrote:
August 3, 2007 - New stable versions of OpenEXR and CTL are now available.
The source code has been tested on Linux, Mac OS X and Windows (Visual
Studio 7 and 8).  Here's a summary of the changes since the last release:

    OpenEXR 1.6.0
        - Reduced generational loss in B44- and B44A-compressed images.
        - Added B44A compression.  This is a variation of B44, but with
          a better compression ratio for images with large uniform areas,
          such as in an alpha channel.
        - Bug fixes.
I've received a bug report about KDE no longer compiling with EXR support with OpenEXR 1.6.0

Here is the report: http://bugs.kde.org/show_bug.cgi?id=148865

Basically, the problem is that this (from ImfStandardAttributes.h)
IMF_STD_ATTRIBUTE_DEF (utcOffset, utcOffset, float)
became
IMF_STD_ATTRIBUTE_DEF (utcOffset, UtcOffset, float)

Was this change intended? Will future versions of OpenEXR contain source-incompatible changes? The reason why I'm asking is to know how to protect this code (i.e. 1.4 and earlier, 1.6 and later, 1.6 only, etc)

Brad




reply via email to

[Prev in Thread] Current Thread [Next in Thread]