Printing says "complete" in the logs but job's "complete" event hasn't fired

[tresf]

When the "PRINTED" event fires from Wmi, it will send the "COMPLETE" status back to the API.

tray/src/qz/printer/status/job/WmiJobStatusMap.java

Line 20 in 875c703

PRINTED(NativeJobStatus.COMPLETE, 0x00000080), // Job has printed

Unfortunately, we use near identical nomenclature when the job is accepted by the spooler:

tray/src/qz/utils/PrintingUtilities.java

Line 152 in 875c703

log.info("Printing complete");

The above can cause confusion when a developer is monitoring job data from both the logs and the API.

[Vzor-]

Maybe it would make more sense to say log.info("Print started") or log.info("Job started")

At that point we only really know the job has been uploaded to a buffer somewhere, be it in a spooler or direct to a hardware buffer.

[tresf]

@Vzor- how about

log.info("Print job spooled successfully");