Posts by support

The latest build of WPTools 7 is 7.33 - it was posted yesterday. I recommend to download the most recent build.

Which version is this - it works fine in my tests.

You need to also subtract vWp.Header.LeftMargin

Further more, vWp.InputString(CRLF) is probably not required.
If you need a second paragraph use vWp.InputString(#13)

Hello,

PDF is possible using our component wPDF. Only a few properties must be set and the procedure wPDF.Print must be called.

wPDF is optimized to work with WPTools and will also export hyperlinks and bookmarks.
It can also embed the JPEG used inside WPTools directly without recompression.

Regards,

Julian Ziersch

Thanks,

you are right - somehow the
{$I PDFLicense.INC}

was deleted in this unit.

The problem was solved by windows update KB3185614 which was installed today.

Yes,
I can provide a discount coupon. You should only pay the price difference.

When using WPViewPDF you can specify the printer name. With pdfPrint there is an option for this, otherwise use the command
COMPDF_SelectPrinter = 35; // par=printer name

When used as plugin for ImageEn WPViewPDF will "only" convert pages of the PDF file into a bitmap which will then be displayed and controlled by ImageEn.

So it should be possible to create a crop of the image. If zooming is required, the image must be extracted at a higher resolution.

It is not possible to make PDF annotations, jump to pages, bookmarks or links. If you need this, you need to use the regular WPViewPDF edition, not the "MakeImage" version.

With WPViewPDF Standard you can zoom, jump to pages, click on links.

With WPViewPDF PLUS you can also save the PDF file you loaded before including all the annotations you added.

There is apparently a fix for the print problem available now:

You will need the product WPViewPDF to sho, print and, with the "PLUS" edition also manipulate the PDF file.

WPViewPDF can show several PDF files as if they were just one. It can also delete/hide and also reorder the pages.

This makes it a great tool to implement a print preview.

Thanks for this hints.

When using the DLL in your application please make sure that all developers who are working on this application are proper licensed for WPTools.

TextDynamic 7.31 is available now.

It integrates the latest changes to the editing and PDF engine. It also solves a possible printing problem which was introduced by a Windows update last week.

Sure, you can send a file to me. Emal as usual: support@wptools.de

WPViewPDF cannot change a PDF file to make it a PDF/A since such change requires
- embedding of all fonts
- adding of layout marker on PDF pages
- changing the color format

Julian

To fix this error in the WPTools code please locate

Printer.EndDoc;

and insert the line
Printer.Copies = Printer.Copies

after it. This resets the printer object.

To fix this error in the WPTools code please locate

Printer.EndDoc;

and insert the line
Printer.Copies = Printer.Copies

after it. This resets the printer object.

19.8.2016

A recent windows update as introduced a problem which affects the runtime used by WPViewPDF.

Although the print dialog works fine, multiple prints with either the PRINT command or pdfPrint can fail on some printers.

On 22.8.2016 we posted updates to WPViewPDF V3 and V4 builds which integrate a fix for this problem.

When printing from WPTools you can use this workaround as a quick fix:

In my tests this solves the problem. It causes a reassignment of the internal DevMode structure, something which appears to be required after the windows update.

BTW: The PrintDialog is not affected by this problem so its use may be an intermediate solution.

Julian

I now found out - the error does NOT happen if I do this:

This means, you can assign a new printer Object using

SetPrinter(prn).Free;

to fix the problem - but the solution in next post appears to be better.

I now got it too. It happnes with Acrobat Destiller, but not with cutePDF and not with Epson driver.

It is not caused by any wptools code, please see my post and example code here:

When printing from WPTools you can use this workaround as a quick fix:

In my tests this solves the problem. BTW: The PrintDialog is not affected by this problem.

Julian