You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if we could override the error callback handler for RgbaInputFile.
The default error callback dumps error messages on stderr and that might be undesirable.
For most of the InputFile classes it is already possible to set custom error callback by constructing with ContextInitializer, for example: MultiPartInputFile ifile( fileName, ContextInitializer() .silentHeaderParse (true) .strictHeaderValidation (false) .disableChunkReconstruction(false) .setErrorHandler(customExrErrorHandlerCb) );
Such constructor is not implemented for RgbaInputFile, AcesInputFile and possibly other classes.
The text was updated successfully, but these errors were encountered:
yes, now that we have replaced the lower level reading functions, the next release of openexr will swap out the writing classes, and then the "other" / secondary classes like rgba input and aces after that. Given we are in a mode of simplifying and modernising, we are making one layer of changes at a time to make sure we are able to quickly react if we break something. If you want to propose a patch to pass through the context to the multipart input file internally, happy to accept that, but otherwise just haven't got to it yet.
It would be nice if we could override the error callback handler for RgbaInputFile.
The default error callback dumps error messages on stderr and that might be undesirable.
For most of the InputFile classes it is already possible to set custom error callback by constructing with ContextInitializer, for example:
MultiPartInputFile ifile( fileName, ContextInitializer() .silentHeaderParse (true) .strictHeaderValidation (false) .disableChunkReconstruction(false) .setErrorHandler(customExrErrorHandlerCb) );
Such constructor is not implemented for RgbaInputFile, AcesInputFile and possibly other classes.
The text was updated successfully, but these errors were encountered: