I just tried the field renaming thing again. I am attaching what I used as the second file of the merge (copy of the first but with Person-TFN renamed to Person-TFN-1 and the extra field/boxes deleted so it is visually obvious it is different). I also altered the demo project code so it would find a...

Hi, yes I assumed it was very likely related to the name overlap, but I will make two observations: * I would have expected at least one of them should stay unbroken. * The output files work in (current) Adobe and old PDF-XChange Viewer v2.5. Of course it is up to Tracker Software whether these obse...

Not sure whether to be happy or sad that it wasn't just me doing something wrong :wink: But very pleased you've been able to reproduce the problem. Yes, I do understand that Core won't actually run the javascript - but if the javascript stayed where it was supposed to be, and the NeedAppearances fla...

Okay, here is a sample project that reproduces the problem pdf seen in my prior post. That PDF * In Adobe Acrobat and PDF-XChange Viewer v2.5, will open and keep its javascript associated with Format Value on field "Person-TFN". This javascript makes sure the input of "123456789"...

Thanks for the correction. Next stage in isolation I have a simplified PDF and used the same document twice in my merge. When I import field data into the merged file and write to the field AND set NeedAppearances the Format Value javascript disappears on open in PDF-XChange v7 (not Adobe or PDF-XCh...

I may have narrowed it down... The fields in question use javascript to re-format tax-file-numbers from "123456789" to "123 456 789" - for display, the exported value remains the same. For this reason I have been setting the NeedAppearances flag in the acrofields dictionary. What...

I've been using Doc.Pages.InsertPagesFromDoc to combine PDF documents. When I merge two PDFs that contain fields with javascript, everything seems to go okay but when I open resulting PDF in PDF-XChange Editor (v7 327.0) the Format Value custom action scripts seem to have disappeared - the field pro...

Thanks, I look forward to trying it out when the release makes its way to available.

Hello GeoffW, That when calling the function "idoc.Pages.Get_Count" that returns the interface, creates an "invisible" variable - an interface link, for which at the end of the procedure, in connection with its output from the zone of visibility, called _IntfClear. And the objec...

This is an old one - see this post - I was just wondering if "nearest future" was any closer now than it was 2.5 years ago? I would point out that in that 2.5 years (at least) that it has not been implemented, no one has gotten around to updating the documentation to mention this fact - le...

Sasha - Tracker Dev Team wrote:Hello GeoffW,

Our Delphi expert is away for vacation for 3 weeks - please bump this thread again when he will be available.

Cheers,
Alex

Bump

Thanks. My guess is that it probably won't make a huge difference either way, but I suppose I should test some large PDFs before going into production.

I had no idea that I could not copy content between documents. I thought content should be content, and the worst that might happen would be that it would not fit on the page. I dare say there are probably good reasons for the limitation but it certainly wasn't obvious to me. Anyway, you're quite ri...

I've included this problem in the demo attached to my other thread (about merging original and text-only pdfs) - so at least you might be able to run that and see whether you get the same problem (or hold onto it for your expert). I'll try to remember to bump this thread later anyway, if I haven't h...

Not sure what limits you may have on attachments to this forum, but here goes ... okay so I had to split it. pdftest1.zip holds the project and sample pdf files needed to reproduce the problems. (I have removed the serial number so you need to insert your own in the source.) pdftest2.zip holds two r...

Core API SDK v7.0 build 326. Delphi v10.2, 32bit project, under a Windows 10 x64 VM. I have an odd problem and I thought I'd ask here to see if anyone else has seen it. The following code should compile with minimal change: procedure TestPdfDoc(const AFilename: string); var idoc: IPXC_Document; page...

As per the subject line, I've been trying merge text-only pages created with a separate OCR process with the original document. The page sizes are identical between the two. I found an example on here from 2012, but it uses PDF Tools v4, a totally different API. I thought Core API SDK should be simp...

Core API SDK v7.0 build 326. Delphi v10.2, 32bit build, under a Windows 10 x64 VM. This has been reported before under various guises in the last couple of years. var idoc: IPXC_Document; begin // lots of work with idoc and then idoc.WriteToFile(PChar(filename), nil, 0); end; In evaluation mode this...