[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Openexr-devel] Behavioural change in InputPart::readPixels()
From: |
Ed Hanway |
Subject: |
Re: [Openexr-devel] Behavioural change in InputPart::readPixels() |
Date: |
Fri, 31 Oct 2014 19:34:03 +0000 |
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: address@hidden [mailto:address@hidden On Behalf Of Halfdan Ingvarsson
Sent: Thursday, October 30, 2014 1:56 PM
To: address@hidden
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
address@hidden
https://lists.nongnu.org/mailman/listinfo/openexr-devel