There are three built-in events in the script file that can be automatically signaled by the printer if they are set. These events are used to synchronize access to the script file.
To signal an event, set the name of the event in the script file. An event name is limited to MAX_PATH characters and comparison is case sensitive. The name can have a "Global\" or "Local\" prefix to explicitly create the object in the global or session namespace.
[EventNames] CommandsProcessed=Global\PNRASCommandsProcessed DocumentSpooled=Global\PNRASDocumentSpooled DocumentCancelled=Global\PNRASDocumentCanceled
|
CommandsProcessed
If you are changing printer settings between print jobs, you must set the CommandsProcessed to the name of an event you have created and are waiting on in order to know when the printer has finished reading the script file and it is now safe to move on and change the values in the script file for the next print job.
This is to ensure that each job is matched with the appropriate settings (thread-safe batch printing in a multi-thread multi-process environment). It is the responsibility of the printing application to create and block the event. The printer will automatically signal the event when it has finished reading the script file.
DocumentSpooled, DocumentCanceled
The DocumentSpooled and DocumentCanceled events are signaled by the printer when the print job has finished being spooled successfully or has failed to spool, respectively.
These events do not mean the conversion process has completed, only that the print job was spooled or cancelled. Once a print job has been spooled successfully then Raster Image Printer will start the conversion process.
