Due to the default communication of an implemented printer using the respective SDK, our job windows are kept opened, because a constant command exchange is required.
Having your printer configured to use a generic communication instead, will allow sending the jobs to the system spooler, therefore processing the job in a faster way and closing the window sooner, immediately allowing you to continue working through the same cardPresso instance.
Note however that when using a generic printer communication, you’ll lose the ability of executing any advanced operations, like special printing or any kind of encoding.
In order to use it though, you must grant full user permissions to our software configuration files.
You can refer to the following document that explains how to do it.
After that, you need to go to our top CP > Printer Drivers menu, set the Printer Model option of your device to “Standard Printer” and its Print Class to “WIN32API“, then restart the program to load the applied changes.
With all that in mind, in case you must stick with any required printer SDK communication, we can only recommend executing a secondary cardPresso process, since you can simultaneously run as many as you want.