The IMG_File and IMG_Format classes have been changed to support deep rasters natively. Because of this, you will need to modify any custom image formats (usually about 10 minutes of work), and make minor changes to code that uses IMG_File.

The major changes are:

1. IMG_File::open() and create() no longer have long parameter lists

for options. Instead, use the IMG_FileParms class to setup the options and pass this object to the methods.

2. IMG_File::read() now returns a pointer to a buffer instead of writing

into a user-supplied buffer. If you want the old behaviour, call readIntoBuffer() instead.

3. IMG_Stat::getDataType() and IMG_Stat::getColorModel() no longer

exist. Instead, IMG_Stat contains a list of planes (IMG_Plane), one for each deep raster image. Call getDataType() and getColorModel() on these objects instead (for RGBA images, this means one extra indirection: getStat().getPlane()->getColorModel()).

4. When opening a custom image format, you must create a plane by

default, either by calling the appropriate IMG_Stat constructor, or by calling myStat.addDefaultPlane(). Then you may set the data type and color model on it.

5. IMG_Format has some additional virtual functions which describe

the format. You will need to override at least two of them, getSupportedTypes() and getSupportedColorModels().

The IMG_File and IMG_Format classes have been changed to support deep rasters natively. Because of this, you will need to modify any custom image formats (usually about 10 minutes of work), and make minor changes to code that uses IMG_File.

The major changes are:

1. IMG_File::open() and create() no longer have long parameter lists

for options. Instead, use the IMG_FileParms class to setup the options and pass this object to the methods.

2. IMG_File::read() now returns a pointer to a buffer instead of writing

into a user-supplied buffer. If you want the old behaviour, call readIntoBuffer() instead.

3. IMG_Stat::getDataType() and IMG_Stat::getColorModel() no longer

exist. Instead, IMG_Stat contains a list of planes (IMG_Plane), one for each deep raster image. Call getDataType() and getColorModel() on these objects instead (for RGBA images, this means one extra indirection: getStat().getPlane()->getColorModel()).

4. When opening a custom image format, you must create a plane by

default, either by calling the appropriate IMG_Stat constructor, or by calling myStat.addDefaultPlane(). Then you may set the data type and color model on it.

5. IMG_Format has some additional virtual functions which describe

the format. You will need to override at least two of them, getSupportedTypes() and getSupportedColorModels().

The IMG_File and IMG_Format classes have been changed to support deep rasters natively. Because of this, you will need to modify any custom image formats (usually about 10 minutes of work), and make minor changes to code that uses IMG_File.

The major changes are:

1. IMG_File::open() and create() no longer have long parameter lists

for options. Instead, use the IMG_FileParms class to setup the options and pass this object to the methods.

2. IMG_File::read() now returns a pointer to a buffer instead of writing

into a user-supplied buffer. If you want the old behaviour, call readIntoBuffer() instead.

3. IMG_Stat::getDataType() and IMG_Stat::getColorModel() no longer

exist. Instead, IMG_Stat contains a list of planes (IMG_Plane), one for each deep raster image. Call getDataType() and getColorModel() on these objects instead (for RGBA images, this means one extra indirection: getStat().getPlane()->getColorModel()).

4. When opening a custom image format, you must create a plane by

default, either by calling the appropriate IMG_Stat constructor, or by calling myStat.addDefaultPlane(). Then you may set the data type and color model on it.

5. IMG_Format has some additional virtual functions which describe

the format. You will need to override at least two of them, getSupportedTypes() and getSupportedColorModels().

The IMG_File and IMG_Format classes have been changed to support deep rasters natively. Because of this, you will need to modify any custom image formats (usually about 10 minutes of work), and make minor changes to code that uses IMG_File.

The major changes are:

1. IMG_File::open() and create() no longer have long parameter lists

for options. Instead, use the IMG_FileParms class to setup the options and pass this object to the methods.

2. IMG_File::read() now returns a pointer to a buffer instead of writing

into a user-supplied buffer. If you want the old behaviour, call readIntoBuffer() instead.

3. IMG_Stat::getDataType() and IMG_Stat::getColorModel() no longer

exist. Instead, IMG_Stat contains a list of planes (IMG_Plane), one for each deep raster image. Call getDataType() and getColorModel() on these objects instead (for RGBA images, this means one extra indirection: getStat().getPlane()->getColorModel()).

4. When opening a custom image format, you must create a plane by

default, either by calling the appropriate IMG_Stat constructor, or by calling myStat.addDefaultPlane(). Then you may set the data type and color model on it.

5. IMG_Format has some additional virtual functions which describe

the format. You will need to override at least two of them, getSupportedTypes() and getSupportedColorModels().

The IMG_File and IMG_Format classes have been changed to support deep rasters natively. Because of this, you will need to modify any custom image formats (usually about 10 minutes of work), and make minor changes to code that uses IMG_File.

The major changes are:

1. IMG_File::open() and create() no longer have long parameter lists

for options. Instead, use the IMG_FileParms class to setup the options and pass this object to the methods.

2. IMG_File::read() now returns a pointer to a buffer instead of writing

into a user-supplied buffer. If you want the old behaviour, call readIntoBuffer() instead.

3. IMG_Stat::getDataType() and IMG_Stat::getColorModel() no longer

exist. Instead, IMG_Stat contains a list of planes (IMG_Plane), one for each deep raster image. Call getDataType() and getColorModel() on these objects instead (for RGBA images, this means one extra indirection: getStat().getPlane()->getColorModel()).

4. When opening a custom image format, you must create a plane by

default, either by calling the appropriate IMG_Stat constructor, or by calling myStat.addDefaultPlane(). Then you may set the data type and color model on it.

5. IMG_Format has some additional virtual functions which describe

the format. You will need to override at least two of them, getSupportedTypes() and getSupportedColorModels().