-
2010.11.30 19:26 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by Toby Thain
- 2010.11.30 19:43 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by Kevin Myers
- 2010.12.01 06:35 "Re: [Tiff] Tiff Digest, Vol 79, Issue 1 - Win32 ReadFile() / WriteFile() heads-up (John Emmas)", by David J Taylor
- 2010.12.01 17:40 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by John Emmas
- 2010.12.01 12:37 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by Phil Harvey
- 2010.12.05 18:05 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by Edward Lam
2010.12.01 08:45 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by John Emmas
On 1 Dec 2010, at 05:15, Bob Friesenhahn wrote:
As far as libtiff using Windows file APIs goes, it can be "cured" by using TIFFClientOpen() to specify use of the desired file access APIs. This requires writing some tiny I/O wrapper functions.
Thanks for all your help with this guys. In the meantime I've discovered something else that could potentially be helpful:-
FILE* f = _wfopen (path, mode); // This is how libgdk_pixbuf opens the file at present
int handle = _fileno (f); // and this is how it gets the (POSIX style) file handle
HANDLE hFile = (HANDLE) _get_osfhandle (handle);
// Potentially, the above could be used somewhere to
// convert to a WinOS handle, as required by tif_win32.c
It's a bit too early in the morning here for me to think too hard about this but at least I have several potential solutions to follow up!
John