At 07:05 AM 6/15/2005, Thomas K�bler wrote:
i have still the problem with the xobjects.
Both Paulo and I asked for you to send us a sample PDF in order to example - I don't recall your responding with a sample :(. Until we see an actual PDF that demonstrates the situation, we are pretty much at a loss to see what happened.
i think it can be on the graphic state of the pdf-renderer. there are the two operators q = savegraphicstate and Q = restore graphic state. when i look at the xobject, there are more q as Q, so perhaps the last savegraphicstate remains in the stack. when a new xobject is render,
That is correct. When the renderer sees a Do operator (for the Form XObject), it keeps the current stack in place, but then "pushes" a new state on the stack (based on some values in the XObj dictionary) and then starts processing the XObject in question. SO if you were to set the stroke color to "red" and then Do an XObject whose first instruction is a "draw line", that line will be red.
it will use this graphic state, so i have to reset the graphicstate when a new xobject will be use.
There is no way to reset a graphics state - you can only "push" and "pop", and they MUST be matched. Mismatched state will cause an error as well.
Leonard --------------------------------------------------------------------------- Leonard Rosenthol <mailto:[EMAIL PROTECTED]> Chief Technical Officer <http://www.pdfsages.com> PDF Sages, Inc. 215-938-7080 (voice) 215-938-0880 (fax) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions
