Back to back print jobs causing problems
Back to back print jobs causing problems
We're using the print driver to capture and convert output to a file (ie. test.pdf). Using default file name option. Works great, unless a user submits two back to back jobs quickly enough that the first file is not gone when the second starts. I'd like to use the append with date/time or unique id, but not sure how to get the file name so my app processes the correct file.
Hello,
This seems like a multithreading scenario, I advise you to use the locking mechanism of CDIntf to make sure that a new print job will start after the previous one has started, so no conflict in the printer configuration occurs.
You can add id or date to the generated filename using the FileNameOPtions.
Fore more information please check 'FileNameOptions' and 'lock()' in the developers' manual 'Common Driver Interface 250.pdf' that you received with the product.
This seems like a multithreading scenario, I advise you to use the locking mechanism of CDIntf to make sure that a new print job will start after the previous one has started, so no conflict in the printer configuration occurs.
You can add id or date to the generated filename using the FileNameOPtions.
Fore more information please check 'FileNameOptions' and 'lock()' in the developers' manual 'Common Driver Interface 250.pdf' that you received with the product.