🚀 go-pugleaf

In article <1989Mar19.023257.20564@ziebmef.uucp> cks@ziebmef.UUCP (Chris Siebenmann) writes:
> I can't comment on why everyone seems to ignore the clipboard, though
>I have a pretty good idea. I can tell you why ComicSetter doesn't use
>it, and it's very simple.
>
> There's no IFF routines that will write to the clipboard, and it's
>not at all obvious how to write them.

Actually, I have seen a few routines that will write IFF to the clipboard.
The latest of these was iffparse.library - although that won't be out of
alpha/beta test for awhile (this is by Leo Schwab and Stuart Ferguson).
When this is finished (and if Commodore picks it up) then I expect that
IFF to clipboards will pick up.

But until then, here is a simple minded kludge.  Instead of writing
out the data directly, use two passes.  The first pass goes through all
the motions of writing stuff out, but will not actually do IO.  Instead,
it keeps tracks of sizes of chunks. Whenever it figures out a size, it
backpatches a table of chunk sizes.  Then on the second pass, actually
write out the data, looking up the correct sizes from the first pass.
The first pass is non-trivial for generalized IFF, but assuming that
you are outputing a known FORM, with a known nesting structure (ANIM's
would be hard, ILBM's easier), it shouldn't be that hard - certainly
lots easier than reading in IFF.
Darin Johnson (leadsv!laic!darin@pyramid.pyramid.com)
	Can you "Spot the Looney"?