Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!mimsy!mojo!russotto From: russotto@eng.umd.edu (Matthew T. Russotto) Newsgroups: comp.sys.mac.programmer Subject: Re: PICT (version 2) files Keywords: PICT files Message-ID: <1990Jun27.162501.16413@eng.umd.edu> Date: 27 Jun 90 16:25:01 GMT References: <9006251132.aa25836@ICS.UCI.EDU> <2582@network.ucsd.edu> Sender: news@eng.umd.edu (The News System) Organization: College of Engineering, Maryversity of Uniland, College Park Lines: 34 In article <2582@network.ucsd.edu> moreland@network.ucsd.edu (John Moreland) writes: >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... > You mean like it ALWAYS has, at least since the 128K ROMs? Try 0x7FFF, though it shouldn't matter. >FLAME ON (Apple?) > > This "pictSize" info is pretty silly anyway. I have written a PICT parser > that does just fine without needing to know how much data is in the PICT > file. All you have to do is read PICT opcodes until you hit the "opEndPic" > (0x00FF) opcode ! [even EOF would do just fine if you think about it.] Yeah, but the PICT stuff goes way, way, way back. Like I said, it hasn't been used since the 64K ROMs (and was patched away even there...) > Apple tends to be a little shortsighted about such closed designs. Almost all > documentation on PICT/QuickDraw, for example, suggests that one would have > little reason to know the "guts" of PICT files since "OBVIOUSLY" PICT files > are always written on a mac... > > APPLE, THE WHOLE WORLD IS *NOT* A MAC ! > >FLAME OFF Closed? PICT was a pretty extensible design, and PICT 2 is even more so. The information for writing both has been available for a long, long time. -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu ][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?