Is it possible to print to the PDF converter developer edition from a shelled application? From what I read I figured that I could activate the printer from within my program and any other application could print to it. Just that the end user has no direct control over the printer properties.
I'm trying to integrate some third party apps that only have command line switches into a document creation app. At this point there is no alternative for me on these apps.
I posted some code in the VB section if you want to see what I'm doing.
Printing from shell?
Hello,
Activating the PDF Printer from inside your application and allowing your users to open another application (MS Word lets say) and print from Word to the PDF Printer is not possible and it is against the license agreement of the Developer version.
It is possible for your however to launch the MS Word application programatically from inside your own VB app and use the Printout function of Word to print, this is possible. In this way your users are using the PDF Printer through your own application.
For more information about licensing, and if you wish to know if the way in which you are using the PDF Converter is within the license agreement please contact sales@amyuni.com
Hope this helps.
Activating the PDF Printer from inside your application and allowing your users to open another application (MS Word lets say) and print from Word to the PDF Printer is not possible and it is against the license agreement of the Developer version.
It is possible for your however to launch the MS Word application programatically from inside your own VB app and use the Printout function of Word to print, this is possible. In this way your users are using the PDF Printer through your own application.
For more information about licensing, and if you wish to know if the way in which you are using the PDF Converter is within the license agreement please contact sales@amyuni.com
Hope this helps.
No this is not a program the end user is running. Nor is it a DLL or Library that ends up being instanced within the process/thread of my application. By using the CreateProcessA command and waiting for an asynchronous call back I believe it's safe to say that this process is running outside the context of my application and you would be unable to determine if this was being run by the end user or otherwise. I guess I need to look for an alternative WINAPI call.
The funny thing is that it actually worked one time yesterday, but I'm unable to reproduce it.
The funny thing is that it actually worked one time yesterday, but I'm unable to reproduce it.
Well it seems that my problem was two fold - Your converter is extremely sensitive to any delay between activation and printing.. stepping through my code during debugging caused problems.
Also I changed my Shell code to use a combination of the builtin VB shell and some WINAPI calls. I don't get the return value now, but at least it seems to work so far.
Also I changed my Shell code to use a combination of the builtin VB shell and some WINAPI calls. I don't get the return value now, but at least it seems to work so far.