Behavioural change in InputPart::readPixels()
Halfdan Ingvarsson <[email protected]>
| Newsgroups | gmane.comp.video.openexr.devel |
|---|---|
| Organization | Side Effects Software Inc. |
| Message-ID | <[email protected]> |
Hello
In OpenEXR 2.2, if no slices are specified in a Framebuffer object, when
InputPart::readPixels is called, it throws an exception ('No frame
buffer specified as pixel data destination.'). In prior versions, it
would just return without reading any data.
Before I determine which side of the fence to patch; was this change
intentional?
Thanks,
- ½
_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel