-
2017.03.17 14:53 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Bob Friesenhahn
-
2017.03.17 15:53 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Dinesh Iyer
- 2017.03.17 16:07 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Dinesh Iyer
- 2017.03.17 17:02 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Bob Friesenhahn
-
2017.03.17 15:53 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Dinesh Iyer
2017.03.17 17:06 "Re: [Tiff] TIFFSetErrorHandler vs TIFFSetErrorHandlerExt", by Bob Friesenhahn
Hi Bob,
It look like I need to to use TIFFClientOpen to open the file and pass in my own routines for reading/writing seeking if I need to pass in client data. Am I correct? This appears to be rather wasteful if all I want to do is pass some client data. Is there a way to force the library to use defaults if one is not provided?
I think you are correct, particularly if the problem occurs while opening the TIFF file. Consider using thread specific data if is easier for you than adding an I/O wrapper.
If there is only ever one thread then global data can work as well.
Libtiff API additions could solve these issues.
Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/