PDF export / posttoweb conflict

cedrickie..

PDF export / posttoweb conflict

in Contributed Library Questions • 3 years ago

Some of you, including myself had some problems with the PDF export recently. We discussed it here :
https://forum.processing.org/topic/pdf-export-not-working-anymore

as we really needed the PDF export and the latest processing version we tried to find where the problem is.
After 3 hours, testing and digging in the source code we realized it is a conflict with seltars posttoweb library.

So in case you are having problems. Try to remove the posttoweb folder from the libraries folder.
Worked fine here and solved our problems.

@seltar: its looks like there is some problem with the PGraphicsPDF.java in your library. Maybe you can check that.

Replies(1)

PhiLho

Re: PDF export / posttoweb conflict

3 years ago

Ah, good catch!
Note: the trick I used to get in memory PDF output is no longer needed with recent versions of Processing, as one can properly extend PGraphicsPDF now:

import java.io.*;
import processing.core.*;
import processing.pdf.*;
// New version, taking advantage of the new PGraphicsPDF implementing my previous suggestions!
public class InMemoryPGraphicsPDF extends PGraphicsPDF
{
@Override
protected void allocate() // Called by PGraphics in setSize()
{
output = new ByteArrayOutputStream(16384);
}
public byte[] getBytes()
{
return ((ByteArrayOutputStream) output).toByteArray();
}
}

I have this in a .java file and I use it as:

if (frameCount >= 10)
{
// Clean up phase
pdf.dispose();
pdf.endDraw();
InMemoryPGraphicsPDF impgpdf = (InMemoryPGraphicsPDF) pdf; // Get the real renderer
byte[] pdfData = impgpdf.getBytes();
[...]

Top Reply