Javascript saveAs() parameter bug SOLVED

[askelly]

PDF-XChange Editor seems to be ignoring the bCopy parameter of the javascript saveAs() function. When bCopy is set to true, a copy of the current file should be created but the currently opened file should remain active in the editor. When bCopy is set to false, a copy of the current file should be created and then become the currently opened file in the editor (after saving and closing the original file). PDF-XChange Editor 6.0.321 is always behaving as if bCopy is false.

Code: Select all

this.saveAs({cPath: "/server/share/filename.pdf", bCopy: true});

[yogi108]

Hi,

I can confirm that the following just tested with extracted pages - document not named -
does not work as desired:

Code: Select all

this.saveAs({
cPath: "/g/myDoc.pdf",
bPromptToOverwrite: true,
bCopy: true
});

The not saved document will be saved under cPath and gets the new name also ....

kind regards,

[Tracker Supp-Stefan]

Hi askelly, yogi108,

I am checking with our devs now and asking them to take a look at the discussed problem.
We will post back here as soon as we have further news!

Regards,
Stefan

[Ivan - Tracker Software]

The issue is fixed in build 322 which should be available in few days.

[yogi108]

Cool!

Thanks a lot

kind regards,

[Will - Tracker Supp]