AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.08.10 22:06 "RowsPerStrip -- tiffdump vs. TIFFGetField", by Mccarty Michael J
2000.08.11 03:41 "Re: RowsPerStrip -- tiffdump vs. TIFFGetField", by Andreas R. Kleinert
2000.08.11 14:21 "Re: RowsPerStrip -- tiffdump vs. TIFFGetField", by Frank Warmerdam
2000.08.11 14:41 "Re: RowsPerStrip -- tiffdump vs. TIFFGetField", by Andreas R. Kleinert
2000.08.11 14:51 "Re: RowsPerStrip -- tiffdump vs. TIFFGetField", by Andreas R. Kleinert

2000.08.11 14:41 "Re: RowsPerStrip -- tiffdump vs. TIFFGetField", by Andreas R. Kleinert

> That better should be "rb".

libtiff automatially assumes TIFF files are binary. This is handled in the platform specific open functions, such as TIFFOpen() in tif_unix.c or tif_win32.c. It isn't necessary for applications to provide the binary flag to TIFFOpen().

Hm. He didn't say, which one he's using. I for example use my own since years.

>> TIFFGetField( in, TIFFTAG_ROWSPERSTRIP, &rps );
>
> Checking "in" for being != NULL and checking

> the return value of TIFFGetField() would be a good idea.

The point of a minimal demonstration program is to show the behaviour in question with the minimum amount of error checking, and other unrelated code getting in the way.

Well, it more looked like a (quote) <snippet>.

--

Andreas_Kleinert@t-online.de  | http://www.ar-kleinert.de             |
Freelance Consultant & Writer | Software Engineering                  |
 *** PerSuaSiVe SoftWorX ***  | x86 Win/Linux, 68k/PPC Amiga and more |

Already signed http://petition.eurolinux.org against SWPAT?