Hi,
I discover this issue in contrast with PDFConv dev ed. Help file, section CDIntfEx.EnablePrinter Method - Note to Developers.
On Win NT platform
- Install or attach a PDFPrinter with PDFDriverInit();
- CALL EnabledPrinter() immediatly after,according with PDFConv help file;
- Call EnabledPrinter() in the EnabledPre() event.
On Win 9x platform
- Install or attach a PDFPrinter with PDFDriverInit();
- DO NOT call EnabledPrinter();
- Call EnabledPrinter() in the EnabledPre() event.
I hope this can be helpful (also then correct)!
Ciao a tutti. (hallo to everybody) [/b]
EnablePrinter() function - different platform usage.
EnablePrinter();
Here I am...
...first... I use PDFConv DevEd to intercept printing from other apps. I use Borland C++ Builder 5 with CDIntF 2.10c (ActiveX interface).
I discover that, on Win9x, if I call EnablePrinter() after PDFDriverInit() (and in a EnabledPre Event,of course), the apps only print once, then the PDFConv Printer became not available.
So u are right : under Win9x users don't have to call EnablePrinter after calling PDFDriverInit(), but only in a EnabledPre Event.
In addiction, on Win9x, U must set SetDefaultName and SetNameOptions
in the EnabledPre Event : in Win2000 u can do it only once.
With 'help file' I mean the 'Common Driver Interface 210.pdf'.
Ciao!
...first... I use PDFConv DevEd to intercept printing from other apps. I use Borland C++ Builder 5 with CDIntF 2.10c (ActiveX interface).
I discover that, on Win9x, if I call EnablePrinter() after PDFDriverInit() (and in a EnabledPre Event,of course), the apps only print once, then the PDFConv Printer became not available.
So u are right : under Win9x users don't have to call EnablePrinter after calling PDFDriverInit(), but only in a EnabledPre Event.
In addiction, on Win9x, U must set SetDefaultName and SetNameOptions
in the EnabledPre Event : in Win2000 u can do it only once.
With 'help file' I mean the 'Common Driver Interface 210.pdf'.
Ciao!