Re: Behavioural change in InputPart::readPixels()
Ed Hanway <[email protected]>
| Newsgroups | gmane.comp.video.openexr.devel |
|---|---|
| Message-ID | <892CC45FE8899F49AD32FB9A147BD89A3B14115D@mailbox10.lucas.alllucas.com> |
I see that check for no slices in several places, some dating back 10 years and the most recent change being from early to mid 2013, which would have been out in 2.1, if not earlier. Which prior version are you comparing to? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Halfdan Ingvarsson Sent: Thursday, October 30, 2014 1:56 PM To: [email protected] Subject: [Openexr-devel] Behavioural change in InputPart::readPixels() 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 _______________________________________________ Openexr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/openexr-devel