Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!telesoft!mclow
From: mclow@telesoft.com (Marshall Clow @telesoft)
Newsgroups: comp.sys.mac.programmer
Subject: Re: PICT (version 2) files
Summary: Just set length to 0
Keywords: PICT files
Message-ID: <808@telesoft.com>
Date: 28 Jun 90 18:40:07 GMT
References: <9006251132.aa25836@ICS.UCI.EDU> <2582@network.ucsd.edu>
Organization: TeleSoft, San Diego, CA.
Lines: 23

In article <2582@network.ucsd.edu>, moreland@network.ucsd.edu (John Moreland) writes:
> I am writing code on a UNIX system which outputs images in PICT format.
> The problem is, at times I need to write the PICT data to a pipe and I thus can
> not "back up" to re-write the pictSize information which has already
> whized by hundreds of bytes ago.  Does anybody know of a workaround ?
> I thought, perhaps, there might be a "magic number" (0, -1, FFFF, etc..) that
> might tell the Mac to ignore the pictSize field and just read till EOF or
> until it sees the "opEndPic" opcode...
> 
> All of the programs I have tried get quite upset (with FFFF for example).

[Flame Deleted}
 
> Thanks,
> John

	Just put a 0 in the picSize field. DTS has reccomended this to
	several developers. Since the picSize field is only 16 bits,
	and pictures can be _much_ larger than 32K ( or even 64K ),
	there isn't any way that that field can alwasy be accurate.

Marshall Clow
mclow@telesoft.com