PDF XChange Forum

Hello David,

If you want to match your regular expression pattern only at the end of a string, you can use $ anchor (similarly to ^ that anchors at the beginning of a string).
For example, the regexp

Code: Select all

ab$

will match "cab" but not "abc".

In the next 10.5 release of the Editor we are planning PDF-XChange specific extensions to the JavaScript API (mostly inspired by Mathew :D ). app.execDialog: Selection tracking for intermediate items in "hier_list_box". An option to disable sorting in "hier_list_box". Multi-selec...

Can you please clarify whether the lost sessions were all created since the last start of the
Editor?
What is a typical uptime of your machine? Do you keep the Editor running in the background for a long time (say, for days) when you do not use it?

In case of abnormal termination of the Editor (including the termination during a forced system shutdown or power off) the changes made to the Editor settings since the last start of the Editor, can be lost. If you keep the Editor running for a long time and then abruptly terminate it, you can lose ...

Hello MedBooster,
What version of the Editor are currently using?
Was the latest case a full reset of the settings or only the sessions were affected?
Did you sessions disappear altogether or only the recently added ones?

Hi Mathew, We will address both issues in the next feature release of the Editor. - tier_list_box intermediate nodes will support selection tracking through a special (with a runtime id to facilitate uniqueness) property that holds a signed integer value - exactly as it currently works for the leaf ...

app.doc is an undocumented property, however Adobe Acrobat implements it as well.

You can use something like

Code: Select all

app.browseForDoc({cFilenameInit:"*.myext"})

This will allow to browse for files with .myext extension.

Hi Mathew,
app.listMenuItems will be implemented in the next release of PDF-XChange Editor.

Hi Mathew,
Please see app.browseForDoc.

Hi Mathew,
To get the foreground document when it cannot be referenced as this, you can use the app.doc property.

Hi Mathew,
The Editor does not explicitly limit GlobData file size but limits the number of persistent properties by 65536.
As of an alternative to persistent global properties, you can consider Doc.createDataObject, Doc.exportDataObject, Doc.importDataObject and related API.

Hello, could you share more information about it? The issue with "undeletable" directory occurred because of discrepancy between the underlying filesystem and Windows API capabilities. The filesystem itself allows trailing spaces and dots in file and directory names while the API can filt...

Hello bkennedy, Thank you. Yes, this is an issue in our product, we will resolve it in a next release of PDF-XChange Tools. You can delete a directory with leading and/or trailing spaces with this console command: rd /Q /S "\\?\<full path to the directory>" For example, if your directory i...

The issue has been resolved. The fix will be available in the upcoming maintenance release of our products (v10.3.1).

Hi Mathew, Thank you. It is a bug. It will be resolved in the next release of the Editor. In the meanwhile you can use this workaround: function myAddAnnot(doc, annotData) { const newAnnot = doc.addAnnot(annotData); newAnnot.name = annotData.name; return newAnnot; } { let partyDate = new Date('1999-...

Hi Mathew,
Thanks, the first issue is already resolved, the fix will be available in the next release of the Editor.

Actually, we have implemented it as a method, not property, to be more consistent with the existing Acrobat API ( Field.setFocus() ).

Hi Mathew,
I was unable to reproduce the crash. Can you please setup automatic crash dumps for the Editor and send us the crash dump file when you get that crash next time? Thanks.

Mathew wrote: ↑Wed Mar 27, 2024 6:25 pm I'll look forward to the day of .hasFocus as an additional property...

The property has been implemented and will be available in the next release of the Editor.

Hi Mathew,
I do not currently see an non-intrusive way to achieve that. We will consider adding hasFocus property to Field object, as an PDF-XChange extension to the Acrobat JS API.

Hi nbmani, Please try this one: app.addToolButton({ cName: "ExtractPagesByKeywords", cLabel: "Extract Pages by Keywords to one PDF file", cExec: "extractPagesByKeywords()", cTooltext: "Extract pages containing specific keywords", cEnable: true, nPos: -1 }); va...

Hello basbeek,

Assuming the organization name has the same pattern as the last and first name (i.e. [A-Za-z0-9_%+-]+),
the regular expression for your first case can be:
\b[A-Za-z0-9_%+-]+\s*,\s*[A-Za-z0-9_%+-]+\s*(?=$[A-Za-z0-9_%+-]+$)

Hi bwelsh_tracker,
We will contact you later today with further steps.
Thanks for your patience.

Thanks.
Were any other applications opened when that issue occurred?
If you are unsure, please open MS Office Word application and leave you computer locked for a while. As you did this with the Editor.

Please create a memory dump of the Editor process when you see it in that state next time.
You can use Windows Task Manager for this:

Then upload the resulting dump file (%TEMP%\PDFXEdit.dmp) here.

Hello bwelsh_tracker,

Please disable Windows Screensaver and check if the issue still persists when you leave your computer for a while.

Hello MedBooster, We are terribly sorry for this. Were you able to load your settings from that backup file before? Can you please send us that backup file? You can use our file service to upload the file. Also, next time you run into the UI settings having been reset, please launch Windows Command ...

Thank you too, Mathew. Your observations really help us to improve our software. I agree, it might be controversial and not intuitive, but our implementation of JS API has to be compatible with Adobe specification, so that documents created by other software will work in the Editor. However, we can ...

Correct

If you have documents open, and set a global variable with a privileged function while it is open, the first unprivileged document to access that variable after setting it will become the owner. I cannot reproduce this behavior, Mathew. Here are my steps: Open those 2 test documents (containing but...

7. Set the global variable again using the trusted function, and go to the other document. It will now be able to access it, and will be the new "owner" of this variable. This does not change the owner of the document. After this step the other document still cannot access the variable. B...

Hello, Finn, According to the Adobe Acrobat JS API specification, Doc.saveAs method can only be called in a privileged context - i.e. either from the JS console or an application initialization script, or by using privilege elevation functions app.beginPriv/endPriv, which, it their turn, can only be...

Hello, Mathew, According to the Adobe Acrobat JS API specification, when a global variable is changed, it becomes associated with the active document (receives that document as a security origin). In non-privileged context it is possible to access only global variables whose origin is the active doc...

Hello, Mathew,
What version of the Editor are you talking about in your previous post?

Hi Mathew,
I just ran your test cases on the latest release candidate build. The issues you have reported above, have been addressed in the upcoming v10.0.1 release of the Editor.
Thank you again.

Thank you, Mathew, for your thorough analysis.
We are aware of certain inconsistencies in our implementation of JS globals.
We are working to address some of the issues (at least) in the next release of the Editor.

Hello, Mathew Even if I make trusted functions, unless the GlobData file is edited manually, or Global Object Security Policy is disabled, that variable name remains blocked. In privileged context all global variables should be accessible, regardless of their origin. If that was your observation, no...

Hi Mathew,
It is really impressive that you keep sharing such a useful and high quality work.
Maybe it makes sense to publish your code in a public source version control service (such as https://github.com/) ? I think this could make your work more accessible to other people.

You can automate copy/paste by using a kind of preprocessor. If you have a C/C++ compiler installed, you can use it for this purpose. It sounds weird but should work. For example, assuming clang compiler (you can download the installer here ), if you have a shared.js file containing declarations to ...

We are thinking on implementing JS module support as an extension to Adobe JS API, but it is not a trivial task, considering all the peculiarities of Adobe Acrobat behaviour we need to conform to. I think, you can use the following workaround for your case: var C = class { // normal class content he...

You are very welcome, Mathew!
Thank you too for helping us improve our product.

This modification of your code should also work: var TRUSTED_GLOBAL_VALS = app.trustedFunction ( function(globalVar) { app.beginPriv(); return { g: globalVar, // name of the global variable get : app.trustedFunction( function (){ let g = this.g; app.beginPriv(); var d = global[g]; if (d) d = JSON.pa...

Hello Mathew, Trusted functions (produced by a call to app.trustedFunction) can only be created from an application initialization or a console script. The fact that your trusted function TRUSTED_GLOBAL_VALS initializes methods of an object, does not make those methods trusted functions themselves. ...

I think excluding script actions from the undo list is very counterintuitive. If I run a script that makes changes on a document, if the undo ignores it, I won't be able to save the changes (PDF-XChange will act like nothing has changed). I have to make a manual change before it even un-greys the s...

Yes, Mathew, you are right about the inconsistency.
We should exclude annotation modification from the undo list as well, when done from script.
We will discuss your proposed feature and let you know. However, it is unlikely to be included in the upcoming release of the Editor because lack of time.

Hi Mathew,
Yes, our support for trusted functions is incomplete at the moment. We are going improve this in the next major release of the Editor. It is expected within the next month.

Hi Mathew,
Yes, annotations added by a script cannot be undone. This behaviour is by design and aims to prevent flooding the undo list with operations that the user can be unaware of.

Hello, Mathew, The issue is caused by using the method util.readFileIntoStream as an unbound function. This is a correct version of your code: // try to make a trust propagator function out of the readFileIntoStream function var trustedReadFileFunction = app.trustPropagatorFunction( file => util.rea...

Can you please provide a working sample of your code that reproduces the issue?
Along with sample input files.
Thanks.

Search found 323 matches