The driver About box shows: PDF-XChange Printer 2012 Version: 5.5 Build 312.1 Windows 7 Professional x64 (Build 7601: Service Pack 1) Interestingly, after resetting my PC, the problem has gone away. (I have the feeling that it must have been working correctly earlier too or I would have noticed it t...

At least under Windows 7, we are finding that the Save As Dialog open appears underneath the app window. It shows up on the Task Bar, but users often don't see it there and thus think the application is hung when it is just waiting on the modal dialog. The problem is particularly bad if the Saver.Sh...

Thanks for the follow-up. I wasn't clear either in what I said or what I was thinking. What I meant was that from the user's perspective, they select the original end-user printer (e.g. in a printer selection dialog box), and then the application recognizes it as the PDF-XChange printer and creates ...

I'm starting to worry about Ivan. Did he ever make it back?
Jack

Fair enough.
Thanks,
Jack

The sample program and a few of these forum posts have reference to a set of DevMode properties, e.g. DevMode.PapSize. But I can find no mention of this in the documentation. It's not clear to me that we need such a feature, as presumably we can access and set all the DEVMODE properties via the Wind...

Understood. Not thrilled, but I can implement a workaround for people who don't prefer to use the locale default size.
Thanks,
Jack
p.s. I'm going to follow up on the DevMode question separately.

In the process of upgrading from the v3 to v5 driver, I noticed that the paper size logic has changed, or I don't understand how it works. Previously (v3), the initial default paper size was determined by the driver Printing Preferences Settings dialog. Now it appears to be forced to A4, regardless ...

Hi, FYI, it appears to me that the online driver API doc has a couple of typos for the above properties. They show in the doc as "Cc" and "Bcc", but I believe they are case sensitive and must be "CC" and "BCC" respectively, i.e. ALL CAPS. (This also matches th...

Just to clarify, in general the descriptive text values (e.g. "True", "False", "ByItem", "256AES", "FitHeight", etc.) normally work as self-documenting versions of the numeric equivalents. This is the only case I've come across where the text didn't ...

It appears to me (from trial and error testing) that the "AllOpened" value of the Bookmarks.DisplayMode property is not recognized, and acts the same as "AllClosed". However, using "0" works as expected. And the other values (e.g. "ByItem" and "OpenToLeve...

I'm using the SDK, as in the CExAPI example. (By "...installed on the server" I meant the SDK/API version of the printer installation.)

The environment is W2003 Terminal Server with Windows 7 RDP clients. When the PDF-XChange Printer 2012 is installed on the server, our application can select and print to it from any client connection. However when the PDF-XChange Printer 2012 driver is NOT installed on the server, but IS installed ...

Beautiful. Works as expected. Thank you!

(Just curious though: how does anyone else figure this stuff out if it's not documented?)
Jack

How can I specify the time stamp server for digital signatures via the driver API? I tried setting it in the driver properties manually (by enabling signing, adding the server, then disabling signing in the driver dialog), which would be ok because there's probably no need to set it on a per-documen...

Brilliant. I'm not sure why I failed to find that article when searching, but in any case it's now clear: a) Hash refers to the "Thumbprint" b) There is no defaulting and no exception thrown - without valid hash/thumbprint, no signature is added c) Hash value must be supplied as an explici...

I'm nearly done converting my app from the old v3 driver interface to the new one, and the main feature I can't get working is digital signatures via the driver API. Note that is a demo mode evaluation (following your own advice I'm verifying that I can get everything to work before purchasing the l...

Thanks for the clarification on the typo. Now on to getting digital signatures to work...

I am working through the various issues in updating our application to support the new V5 COM driver API (vs. the V3 'escape' API). One complication which I'm not sure how to handle is that we use a tree control (SftTree from softelvdm) which supports its own print rendering that is used within our ...

Is the digital signature properties section named DigSig or DigiSig (e.g. DigSig.Enabled vs DigiSig.Enabled )? The User Guide says DigSig , but I get an error when attempting to set any of the properties, which I don't get when using DigiSig . (And the 3.0 version of the driver API used "Securi...

Works like a charm - thanks!

As an aside, is it intentionally undocumented, or is there a later (than April 17, 2014) version of the PDF-XChange Drivers API SDK 2012 User Manual?

Thanks again,
Jack

When the Save.ShowSaveDialog is enabled, the dialog starts in the directory last used in a prior save, rather than in the directory corresponding to the Save.File and/or Save.Path value. You can reproduce this in the CExAPI sample program by just enabling the option. You'll see that the dialog comes...