|
Do it all with PDF-XChange PRO A product suite that includes all of the above PDF products and allows you to do pretty much whatever you want with PDFs  |
|
|
|
|
|
| SDKs for PDFs: | SDKs for Imaging: | Clarion® SDKs: |
|
PDF Related 
|
Imaging Products 
|
Clarion® Developers now have the choice of using our generic SDKs, or downloading our Clarion® specific SDKs which include extra Clarion® classes, templates and examples for fast and easy integration into their Clarion® based applications. |
Knowledge Base Article: KB235 - Created On: Jan 18, 2010 02:28 PM - Last Modified: Jan 8, 2013 10:08 AM
I am currently evaluating the V4 PDF XChange printer driver. I noticed that the sample code was temporarily setting the PDF XChange driver as the Default Printer in Windows. The documentation explains how to do this, but it doesn't say why, or in which scenarios this would be necessary.
Is this a limitation of the product, that it works only if set as the default Windows printer?
As far as our driver is concerned and the need for it to be set as the default printer; this is generally not necessary. However, it is required when a developer's application prints an external file (for example, a Word Document using Word as the Viewer/print output method) and there is no ability to specify programmatically which printer the external application should send the output to (by default, all applications will inherit/use the default printer in this case)
Browse All Articles
Tags: 