On Sun, Mar 09, 2003 at 03:01:53PM +0000, Michael Nordstr�m wrote: > On Sun, Mar 09, 2003, Adam McDaniel wrote: > > Now comes the problem. I have written the code in the viewer to > > support this but I have no idea how to handle support in the python > > parser > > Hmm, I can see more problems than just to make the parser split up the > image; what if I have an image that is VERY wide? You solution depends > on the width being of a "reasonable" size.
Well, I don't see any problem in creating a single image thats 1000 pixels wide and 1 high. Ofcourse, the altmaxwidth/altmaxheight value would cap any runaway issues like that. > I suggested a solution to this problem in June 2000, but (just as in > your case) I needed a parser that could split the image into smaller > parts... Hence my email out to the list :) Here's some more details on DATATYPE_MULTIRECORD as a data record: uid = unique ID paragraphs = always 0 size = number of pieces of the image multiplied by 2 type = DATATYPE_MULTIRECORD (ie, 15) Then the data would be a direct list of uids, one after another, two bytes each. Do you think that might be too simple? In other words, should there be like a MultirecordType structure header to preceed the data that contains a bit more detailed information? -- Adam McDaniel Array.org Calgary, AB, Canada _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
