Beiträge von wpsupport

Update: 11.1.2019 - V7.60

- improved stability of editor

- fixes for 64 bit support

- fixed problems with unicode text typing

Update: 21.2.2017 - V7.33.0.2

- improvements to DocX support and editing and XML support

Update: 26.3.2018 - V7.50

- improvements to double click handling

- updates to PDF engine

This is a bit vague - if you have a demo project using WPTools 8 which shows the unwanted effect I check it out.

Maybe you use tables - I could imagine text can be under an image if it is linked in a different cell - but this is more a problem with the document than a wptools issue.

You can send example files and demo projects (sourcecode, no binary) to support@wptools.de

Dieses Alignment wird evtl. in einer zukünftigen Version für eine gesplitteten Zelle unterstützt, nicht in V8.

Ein neu kalkulieren bleibt einem nie erspart. Irgendwo muss die gesamt summe ja herkommen. Das Datenfeld muss auch nicht die tatsächliche Summe sein, sondern kann auch eine Referenz auf ein "Rechenblatt" ausserhalb sein.

Ja, der event kommt nur bei der Ausgabe, sonst nicht. Das ist auch gerade der Witz und darum ist das System schnell. Für Berechnungen ist das Ereignis nicht zu gebrauchen.

Ich denke Rechnungen mit 250 Seiten dürften auch eher unüblich sein. Hierfür braucht man besondere Lösungsansätze

Wenn es Flaschenhälse gibt, liegen die vermutlich woanders. Ein Thread der im Hintergrund die Seiten abfragt, das wird recht interessante Fehler verursachen.

WPTools ist zwar thread save, aber nicht als Editor sondern als document creator (TCustomRTFEdit) in seinem eigenen environment. In dem selben environment dürfen nicht mehrere threads gleichzeitig auf den Text zugreifen.

Wichtig: WPTools (5 und später) verwendet keine Strukturen die Seiten direkt zugeordnet werden. Es ist komplexer, es gibt Seiten mit Ausgabeobjekten welche dem Text in Absätzen zugeordnet werden. Damit kann der Text eines Absatzes auch auf mehreren Seiten erscheinen, was bei Kopf und Fusstext, aber auch bei Tabellen köpfen und -Füssen regelmässig der Fall ist. Daher kann ich die Frage nicht allgemein gültig beantworten.

Generell kann man aber für jede Zeile eines Absatzes abfragen auf welcher Seitennummer sie ausgegeben wurde mittels einer recht komplexen funktion des TParagraph: function LinePageNr(lin: Integer): Integer;

Wie ich bereits früher schrieb, sollten Sie dynamischen Text mittels Ausgabeobjekten drucken. Diese Ausgabeobjekte müssen die aktuelle Seite vor der Ausgabe (oder dem Druck) auswerten, nicht bei der Formattierung. Die Berechnung passiert also in der paint routine!

Dies ist code aus der Demo: WPReporter_Calc

procedure TWPTableCalc.DoTextObjectPaintCalcEvent(Sender: TObject;
     pobj: TWPTextObj; par : TParagraph;
     page : TWPVirtPage;
     pagenr : Integer;
     textbody : TWPRTFDataBlock;
     var ResultText : WideString;
     PaintCanvas : TCanvas; var UseIt : Boolean);
var formula : string;
    j : Integer;
    sum : extended;
    s : string;
    obj : TWPTextObj;
begin
   formula := pobj.Source;
   if formula='LASTTOTAL' then
   begin
     for j:=page.EmbeddedObjectCount([wpobjTextObject])-1 downto 0 do
     begin
        obj := page.EmbeddedObjectGet(j);
        if obj.Name='LASTTOTAL' then
        begin
          ResultText := obj.Params;
          UseIt := TRUE;
          exit;
        end;
     end;
   end else
   if (formula<>'') and (formula[1]>='A') then
   begin
     sum := 0;
     for j:=0 to page.EmbeddedObjectCount([wpobjMergeField])-1 do
     begin
        obj := page.EmbeddedObjectGet(j);
        s := obj.EmbeddedText;
        if (s<>'') and (s[1] in ['-','0'..'9']) then
        try
          sum := sum  + StrToFloat(s);
        except
          ResultText := 'ERR';
          UseIt := TRUE;
        end;
     end;
     if not UseIt then
        ResultText := FloatToStr(sum);
     UseIt := TRUE;
   end;
end;

In dem Paintcalc event des controls TWPFormulaInterface bekommt man auch die aktuelle Seite und sogar eine Referenz auf Zeichenunterlage "page". Der Code zeigt wie dort alle Felder ausgewertet werde. Dies können auch unsichtbare Felder sein um die vorherigen Summen auszuwerten.

Sie können also in jeder Ihrer Tabellenreihen die aktuelle Summe abspeichern, ähnlich einem laufenden Kontostand auf einem Bankauszug.

Wenn man das TWPFormulaInterface nicht zur Verfügung hat, kann man auch OnTextObjectPaint verwenden.

procedure TForm1.WPRichText1TextObjectPaint(Sender: TObject; pobj: TWPTextObj;

toCanvas: TCanvas; XRes, YRes, X, Y, W, H, BASE: Integer;

PageRef: TWPVirtPage; Modes: TWPTextObjectPaintModes;

const CanvasExtraAttr: TWPPaintExtraParams;

var ContinueMode: TWPTextObjectPaintResult);

und dort PageRef bzw PageRef.pagenr.

Zitat

Damit klappt es ! Das erzeugt zwar jetzt noch einen zusätzlichen Absatz, den ich dann wieder löschen muss, aber das kann man ja machen.

Was ist eigentlich der Grund dafür, dass das erste \par entfernt wird?

Das ist ein Fehler - er wird im nächsten Build nicht mehr sein. Eigentlich sollte der Absatz *nach* dem text entfernt werden (DeleteParagraphEnd) da der RTF reader immer einen Absatz am Ende anhängt. Dies liegt an dem \par am ende.

Zitat

Es handelt sich um eine Druckausgabe. Der User gibt an mehreren Stellen Texte ein, die ich dann zu einem Dokument zusammenfasse. Dazu lege ich jeweils einen Absatz an und befülle diesen mit den Texten vom User. Diese können durchaus mehrere Absätze oder (im schlimmsten Fall) auch Seiten haben.

Die "normale Load Funktion" wäre dann Richtext.LoadFromString()? Die gibt mir leider den Paragraphen nicht zurück.

In einen Absatz laden, könnte durchaus zu Problemen führen, da sie für das reine Aneinander hängen von Texten eigentlich nicht gedacht ist. Es wird eine besondere verschachtelte Struktur erzeugt wenn man dies benutzt.

Man kann den aktuellen Absatz mit ActivePar auslesen oder CPPosition lesen und schreiben. Damit kann man die Position nach dem normalen Laden verändern.

Es ist ungewöhnlich mehrere Absätze in einen einzelnen Absatz zu laden. Vermutlich wollen Sie in die Absatz Kinder laden, denn dies ist eigentlich das, wofür es par.Load gibt. (Ansonsten könnte man ja gleich an der Cursor Position einfügen und dafür die normalen Load Funktionen nutzen.)

So werden dann Child Paragraphs erzeugt - dies passier in einer Tabellen Zelle immer

WPRichText1.ActivePar.LoadFromString(str,[wploadpar_AsChildrenPar]);

Die Höhe berechnet sich aus der Höhe der Zeichen wie sie auch im Text angezeigt werden. Wenn ein Absatz leer ist, dann wird bei der Berechnung die Default Fonthöhe herangezogen sofern für den Absatz keine default attribute verwendet werden, wie dies nach dem Laden aus RTF der Fall ist.

Die font höhe aus den Absatzattributen (WPAT) wird hier nicht verwendet.

Die Einheit ist, wie bekannt, Memo.CurrentYPixelsPerInch, normalerweise ist dieser Wert 600. Also nicht twips.

Ich wiederhole gerne mein Angebot für Ihre Problemstellung als Auftragsarbeit einen Lösungsvorschlag zu erarbeiten!

Nach dem Einfügen eines Textes kann dieser nicht direkt ausgemessen werden.

Erst nach einem Reformat kann dieser ausgemessen werden und table.height liefert dann das richtige Ergebnis genauso wie Ihre Schleife.

4 * 106 = 424!

Nächste Woche

Ja, ist geplant.

Welche Rechteck angabe ist denn gewünscht? Screenkoordinaten oder PDF Koordinaten?

Was bereits geht ist ein rechteck aufziehen und dann entsprechend zoomen. Dies geht mittels

COMPDF_Zoom = 43; //! Zoom to IntPar ; if IntPar=0 retrieve zoom!

// If StrPar='MP' it will center to mouse position

// If StrPar='RECT' and called in SelRect Event it will zoom to selected rectangle

// Use a negative value to preset a zoom value for next call to COMPDF_GotoPage

Man übergibt also einen string parameter mit dem wert "RECT". Das ganze funktioniert nur innerhalb des SelRect events.

Das recheck per code setzen geht derzeit nicht.

WPTools hat dafür die Textobjekte, diese können über code ausgegeben werden. Dabei kann der Inhalt der aktuellen Seite ausgewertet werden.

Ein Verândern des Textes während des Formatierens ist nicht vorgesehen

WPViewPDF 4.7.1.2 release 7.3.2019

- fixes problem with 64bit DLLs in last build - they were not loading

WPViewPDF 4.7.1.1 release 2.3.2019

* PLUS edition: improved form handling

WPViewPDF 4.7.1.0 release 27.2.2019

+ added some support for FunctionType 4 separation color

- fixed "stack error" exception

WPViewPDF 4.7.0.0 release 25.2.2019

+ new command: COMPDF_SetAnnotEditModes modifies the way the TAB key works in formular mode

* improved TAB handling and scrolling formular mode

WPViewPDF 4.6.5.1 release 21.1.2019

+ new: Drag&Drop support with Delphi and TWPViewPDF.

To use assign events OnDragOver and OnDragDrop.

- fix stability problem when drag&drop was used with Delphi 10.3 Rio in 64bit application.

WPViewPDF 4.6.4.6 release 12.1.2019

- improvements to 64 bit DLL

- fix for bullet sign

WPViewPDF 4.6.4.5 release 13.12.2018

* Updated documentation for command COMPDF_Attachment_AddAF.

--> Please pass the id returned by this command as second parameter when you load the data which should be used by a PDF attachment.

- fixed problem when saving PDF file with attachments

WPViewPDF 4.6.4.4 release 5.12.2018

- correctly hides text written with Tr3 mode but still allows text selection

WPViewPDF 4.6.4.3 release 30.11.2018

- improves compatibility to PDF files which save spaces in front of object numbers

- solves AV problem on problematic CCITT data

WPViewPDF 4.6.4.1 release 19.10.2018

- when rendering draw objects with right aligned text into the PDF the text was not positioned correctly

- when rendering draw objects with centered aligned text was not positioned correctly

WPViewPDF 4.6.4.0 release 16.10.2018

* PrintHDC, GetMetafile does not cache the page commands anymore which reduces the

memory consumption if a large number of pages are processed.

- fix problem with certain images with indexed color

- fix problem that font size was not read from widget annotations (DA parameter)

- fix line breaks in multi-line edit fields

* .NET interface supports new parameter options in AddDrawObject()

WPViewPDF 4.6.3.3 release 10.9.2018

- fix cache problem which caused large memory consumption when extracting text

+ command COMPDF_NoViewer can be used to temporarily disable the rendering for fast loading and text extraction

- Annotation Flags "F" were not handled correctly. They are now correctly loaded from prp.v.F

This causes annotations which are supposed to be invisible to be hidden (though they are selectable in certain operation mode)

WPViewPDF 4.6.3.2 release 22.8.2018

+ command COMPDF_RenderDrawobjects now returns the number of rendered objects.

Use Bit 8 in the parameter to only count the objects.

- fixed problems when writing check boxes in PDF forms

* improved text extraction (more exact X coordinate calculation)

WPViewPDF 4.6.3.1 release 14.8.2018

- the scaled print mode (COMPDF_PrintUseScaling) also set the paper size which worked against the purpose

WPViewPDF 4.6.3.0 release 9.8.2018

- fix cmap reading error when <..> codes were on the same line

- fix problem with acroform objects which used fields as indirect reference

- fix problem with PrintDialog loosing focus on Alt+TAB

- COMPDF_ACTION_WRITE can be used to localize the action captions.

The problem that some sub menus were not been localized has been fixed.

+ understand Encoding: UniGB-UTF16-H

WPViewPDF 4.6.2.3 release 24.7.2018

* change default value for COMPDF_GetTextSetOptions = 272 - set bit 2 if you need y position written as text baseline position (=default) or clear bit 2 to save the top position. (Consistency to WPViewPDF V3)

WPViewPDF 4.6.2.0 release 21.7.2018

+ new command: COMPDF_GetTextSetOptions (=272) - set bit 2 if you need y position written as text baseline position or clear bit 2 to save the top position

WPViewPDF 4.6.1.0 release 2.7.2018

+ The text extraction method has been revised for better detection of lines of text, even if not

printed at the exact same vertical position.

WPViewPDF 4.6.0.0 release 29.6.2018

+ command COMPDF_SinglepageMode,2 can now be used to toggle the single page mode.

* improve compatibility with PDF files which use Encoding as indirect reference.

WPViewPDF 4.5.3.0 release 29.5.2018

- fixes problem with XForms

- fixes problem with separation color used for stroking

* updated Demo DLL

WPViewPDF 4.5.2.5 release 27.4.2018

- fixes problem with annotations (caused by 4.5.2.2 - XForm handling)

- check annotation with CA property = 8 now shows X

WPViewPDF 4.5.2.3 release 20.4.2018

+ command DONTSETDEVMODE can now be used to disable the landscape detection on w>h

- workaround for PDF files which use incorrect ASCII85 encoding

WPViewPDF 4.5.2.2 release 11.4.2018

* improve ToUnicode interpreter to not fail on incorrect range

* limit size of intermediate bitmap used for PrintHDC when UseRotation=true

* improve PDF compatibility

- handles inverted CMYK image stream

- use current state as default state for XForm painting.

Solves problem if XForm does not define any colors.

WPViewPDF 4.5.2.0 release 28.3.2018

- fix problem with "use rotate" parameter of PrintHDC

WPViewPDF 4.5.1.0 release 8.3.2018

- fix internal AV introduced by new "scn" handling

- fix redraw issue after text selection

WPViewPDF 4.5.0.0 release 7.3.2018

+ command COMPDF_Get_XMPBuffer can be used to read the loaded PDF metadata.

The IntParam is used to select the loaded PDF-File to examine. (default=0).

It is also possible to provide the NAME of the PDF-File to check in the StrParam.

The Result Value = -2 if IntParam is not valid or the provided PDF filename was not loaded before.

- invisible text can now be selected

- Rendering of annotations and draw objects used wrong position when a crop box was used in PDF.

- improvement to comment handling for postscript page description

- improvement of text highlight to annotation conversion. (AddHighlightAnnotationForText)

- MouseUp event was lost when internal code handled mouse event as well.

+ AddHighlightAnnotationForText now accepts Alpha parameter in Range 0..255

WPViewPDF 4.4.4.0 release 7.2.2018

* the PDF to text feature now adds spaces if it detects gaps between rendered text elements

this feature can be switched off with Command(COMPDF_DontSynthesizeSpaces,1)

+ COMPDF_Ann_ModifyAddProps can now be used to set the "HighlightType"

* improved text selection and highlighting

WPViewPDF 4.4.3.3 release 22.1.2018

* Handle the case when '-' was used in image draw operation and encoded as #2D in dictionary

+ accept PDF 2.x as input format

WPViewPDF 4.4.3.2 release 15.1.2018

* do not write MarkInfo if not all PDF files which are merged use this flag

- fix problem in CMYK conversion

WPViewPDF 4.4.3.0 release 15.12.2017

* improvement of handling for embedded objects which are using HexEncoding

+use Command(COMPDF_SetSaveMode, 8192 * 1024) to save all fonts, not just the ones which are used.

- fix problem that draw objects do not work correctly with SetGlobalParameter('ReduceMemoryUsage=1'

+ better alignment of the view panel relative to the thumbnail/bookmark view

WPViewPDF 4.4.2.0 release 8.11.2017

+ detect corrupted PDF data with garbage at end of file

* optimized detection of fonts which are using 2-byte CIDs

* improved support for embedded fonts

WPViewPDF 4.4.1.0 release 3.10.2017

- write the flag /EncryptMetadata when file encryption was activated

+ use command( COMPDF_SetSecurityMode, 1+4096) to activate encryption also of metadata in 40 bit or

command( COMPDF_SetSecurityMode, 2+4096) in 128 bit security mode.

WPViewPDF 4.4.0.0 release 22.9.2017

- fix problem when saving PDF file with named destinations

- fix problem when displaying bookmarks

* improvement when saving PDF which contain unicode strings in name array

WPViewPDF 4.3.4.0 release 20.9.2017

+ use command(COMPDF_SetSaveMode, 8192 * 256) to always write NeedAppearances=true

+ use command(COMPDF_SetSaveMode, 8192 * 512) to always write NeedAppearances=false. This fixes the problem that AcrobatReader asks to save changes.

+ experimental: Use SetGlobalParameter('ReduceMemoryUsage=1') to reduce the storage of path objects.

That helps with PDF files which use a lot(!) of text paths on a page but can slow down repaint.

WPViewPDF 4.3.3.0 release 7.9.2017

- COMPDF_GetPrinter could not be used with CommandGetStr

- fix problem with desired width/height with GetImageExt

WPViewPDF 4.3.2.0 release 26.7.2017

- update to font character selection

WPViewPDF 4.3.1.0 release 10.7.2017

+ using the command COMPDF_Ann_Undo = 560 it is now possible to disable and enable the UNDO buffer.

use Command(COMPDF_Ann_Undo, 4) to disable, Command(COMPDF_Ann_Undo, 5) to enable.

WPViewPDF 4.3.0.0 release 21.6.2017

+ flatten form (annotations) when saving the file

+ option DeleteFormFields=1 in pdfMerge()

+ option FlattenFormFields=1 in pdfMerge()

+ The save modes can be specified with SaveToFile command

+ The save modes can be specified with pdfMerge as parameter SaveMode=x

- fixed memory issue caused by undo system

WPViewPDF 4.2.5.0 release 31.5.2017

+ COMPDF_Ann_ModifyAddProps can now be used without updating the screen at once. Add option 16.

- fix exception error which could happen with some corrupted PDF files.

WPViewPDF 4.2.4.0 release 11.5.2017

- fixed hyperlinks to named destinations

WPViewPDF 4.2.3.0 release 3.5.2017

- fix problem with wrong character width when font height in PDF was negative.

WPViewPDF 4.2.2.0 release 20.4.2017

- fix a stability problem when reading annotations which were using quadpoints

+ detect "caret" annotation

* improve strikeout annotation

WPViewPDF 4.2.1.0 release 5.4.2017

- fix problem when ScreenToPage was used directly after a LoadFromFile.

WPViewPDF 4.2.0.0 release 29.3.2017

- fix problem when saving attachments from PDF

+ add support for Delphi 10.2 Tokyo

WPViewPDF 4.1.9.9 release 15.3.2017

+ new option for pdfMerge: COPY_NON_ENCRYPTED=1 will copy the original file if only one source file was

specified and that source file was not encrypted.

+ new option for pdfMerge: PASSWORDxxx=1 sets a password (xxx=1..999) in a list of passwords used for the loaded PDF files.

+ Use SetGlobalParameter('DrawImageBands=1') to make WPViewPDF draw large monochrome bitmaps using several bands instead of

one big bitmap. This has been introduced to increase compatibility with certain printers. (Experimental - may become default in future)

WPViewPDF 4.1.9.8 release 9.3.2017

+ support for text RenderMode 1 (outlined text)

- fix for gray scaled JPEG2000 encoded images

* when writing PDF files Signature annotations are written together with the accompanied field

WPViewPDF 4.1.9.6 release 2.3.2017

- fix problem for certain JBIG2 images which showed up after last build.

WPViewPDF 4.1.9.5 release 24.2.2017

* property SecurityOptions defaults now to []. Please check if it is required to disable the save functionality.

* includes a workaround to avoid printing problems of pixel based barcodes on some printers

* improves text find method

WPViewPDF 4.1.9.4 release 18.2.2017

+ the VCL defined a new method AddHighlightAnnotationForText

+ when adding a highlight annotation it is possible to create a non rectangular area to cover the previously found text.

Use "atfoundtext=1" in the options. Note: x,y,w,h must also be provided!

- fix a flicker problem when highlighting text

WPViewPDF 4.1.9.3 release 9.2.2017

- fix problem with FindText - the scrolled position was slightly off

WPViewPDF 4.1.9.2 release 3.2.2017

* the text export now calculates more accurate positions in the xyhtml code

* find text returns better coordinates

- fix: when a PDF file used a cropbox the annotation frame was drawn at a wrong position

- acrofields with auto size text were always written with fontsize 12

WPViewPDF 4.1.9.1 release 27.1.2017

* avoid problem with PDF files which use comment in the page description

+ MergeText now uses COMPDF_BeginUpdate/COMPDF_EndUpdate to improve performance

WPViewPDF 4.1.9.0 release 26.1.2017

- fix for command COMPDF_ACRO_SET which can be used to set the acrofields used by a PDF form

WPViewPDF 4.1.8.4 release 4.1.2017

- fix a problem when saving some rare PDF files

* improve scrolling in thumbnail view

WPViewPDF 4.1.8.3 release 23.12.2016

* includes workaround for incorrect PDF files which miss endobj markers.

WPViewPDF 4.1.8.2 release 21.12.2016

* bitmaps with of bit height will now be printed without any anti alias. This

fixes problems with barcodes which were printed with some shading.

- in scanned documents some characters showed up when the font was not defined.

- display characters corrected when CIDtoGID and ENCODING cmap was used.

* improved interpretation of cmap definitions

* the handliung of ligatures (fi) has been improved

WPViewPDF 4.1.8.1 release 13.12.2016

- fixes a problem with some images introduced in last release caused by compiler issue

* fixes DEMO expiration problem

WPViewPDF 4.1.8.0 release 7.12.2016

+ Improvments to PDF-Workbench. This object can be created be used without having to use a window handle.

* WPViewPDF also works fine to print the PDF pages on a HDC. No window handle is required - PrintHDC

- fixes a memory leak which sometimes occured when PDFs were using monochrome JPEGs

+ using command COMPDF_UseGDIPainter with parameter = -2 it is now possible to select the standard, non

GDI+ painter to be used by PrintHDC and GetMetafile.

+ added a Delphi demo which is using PDF-Wokbench object.

+ added fall-back for font output in case the font could not be loaded by integrated font engine

WPViewPDF 4.1.7.4 release 24.11.2016

- fix an internal exception when creating a field

* don't save AcroForm object if it was detected to have no fields.

+ the parameter "F" of a widget controls if the widget is printed or not.

Use SetGlobalParameter('AddFieldDefaultF=1') to make WPViewPDF add the value F=4 to all

fields which do otherwise miss this property.

WPViewPDF 4.1.7.2 release 22.11.2016

+ event: OnChangePageSelection

+ Use SetGlobalParameter('rotatemeta=1') if you need to extract pages as metafiles with applied page rotation.

Instead of SetGlobalParameter(stringvalue) it is also possible to call Command(200000, stringvalue)

WPViewPDF 4.1.7.0 release 18.11.2016

- fix: It was not possible to move a page to last position when a page was deleted

- fix problem with special CID font

+ impove drag&drop in thumbnail view

+ added support for color inline graphics

WPViewPDF 4.1.6.4 release 18.10.2016

- fix problem with wide outlines in some texts

+ added support for subforms in AcroForms.

* more strict interpretation for Bit 10 in security P flag (=extract graphics and text)

WPViewPDF 4.1.6.2 release 6.10.2016

* ignore path drawing inside text blocks (workaround for some PDF files)

* improved display of FreeText annotations

- VCL: In API FindText a variable was named DontGoToPage although its meaning is GoToPage - it has been renamed to "GoToPage"

- fix for Y position when FindText was used.

- FindNext was broken

WPViewPDF 4.1.6.0 release 28.9.2016

- improves saving of highlight annotations

- fixes problem with loaded multi line selection

+ during adding highlights the user can press CTRL+Z to undo the last change

WPViewPDF 4.1.5.7 release 15.9.2016

* enhanced font width measurement

* enhanced character location in CID fonts

- fix problem with encrypted PDF files which use a non-standard FileID

WPViewPDF 4.1.5.5 release 31.8.2016

- drag over caused AV in Delphi XE up to 10.0

- move pages did not work correctly when pages were deleted before. This problem has been fixed.

WPViewPDF 4.1.5.4 release 22.8.2016

* we integrated a fix for a possible problem when printing documents multiple times without using the print dialog.

This problem showed up in some other applications after the windows update released 19.8.2016 and also with the pdfPrint() function.

(To switch off this fix use SetGlobalParameter('printerfix=0'), to switch it on again us SetGlobalParameter('printerfix=1') )

* do not always draw hairline around filled areas

WPViewPDF 4.1.5.3 release 2.8.2016

- fix problem when 64bit DLL was used with .NET 4.5

- fix problem with lost image resource when saving PDF

WPViewPDF 4.1.5.2 release 28.7.2016

+ using command COMPDF_MODIFIED it is possible to check if the contents were modified by the user, i.e. if pages were moved.

+ new function pdfMakeImageEx can load the PDF data from a IStream and save one ore multiple images to an IStream.

+ new unit: wpcubed_pdf_plugin has been added to use WPViewPDF with ImageEn, the powerful image component for Delphi.

+ new WPViewPDF Edition "WPViewPDF MakeImage" which supports pdfMakeImageEx only.

WPViewPDF 4.1.5.1 release 15.7.2016

- do not show OCR text on certain scanned document

+ support for Win2151Encoding (not standard)

WPViewPDF 4.1.5 release 30.6.2016

* improved rendering code for auto-textheight multiline freetext annotations

+ when saving a PDF the Catalog/AF array is also saved.

* the saving of names dictonaries has been changed so save names to merged documents, too.

+ new ViewOption: wpDisableAnnotTextEditInEditMode

+ new commands to add file attachments to a PDF file

COMPDF_Attachment_AddAF, COMPDF_Attachment_SetData, COMPDF_Attachment_SetProp

+ new DLL methods to create a non-visual "PDF workbench". With the created object most

viewer commands can be used to examine and manipulate PDF data. This can be helpful if you need

a powerful PDF tool in C++.

* editor will switch into text edit mode of text annotations on click on selected object, not at once

WPViewPDF 4.1.4'' release 20.6.2016

- fix display of some (OCR) fonts which are not embedded but loaded from system

WPViewPDF 4.1.4' release 14.6.2016

- fix a checkbox saving glitch

WPViewPDF 4.1.4 release 8.6.2016

- URI links were not working - now OnHyperlinkWWW can be used

+ scale the PDF pages when saving to a new PDF file

New commands: COMPDF_SaveScaledPDFMode, COMPDF_SaveScaledPDFSetX and COMPDF_SaveScaledPDFSetY

When using Delphi you can use the method ActivateScaledPDFWriting to enable the scaling.

WPViewPDF 4.1.3' release 17.5.2016

+ annotation flattening mode UseOriginalDataForRendering

+ allow the sign ~ to be used in PDF names

You are posting in the WPTools 8 section - I had to presume you were using this.

Please use the code published for WPTools 5 to insert images, there are some examples.

You can load an image from file or stream.

It's really like I wrote, you can simply add text and images like you would usually using code.

procedure TForm.WPRichText1MailMergeGetText(Sender: TObject;
  const inspname: string; Contents: TWPMMInsertTextContents);
begin
   (Sender as TWPCustomRtfEdit).TextObjects.InsertCopy(Image1.Picture.Graphic);
end;

You can insert another image, use InputString to insert some text...

But if you do so, you need to leave Contents unchanged. Also do not use Contents.MergePar or anything else inside Contents.