Not all jobs are recieved by printer

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. applet.setDocumentsPerSpool("1");
2. applet.print() // f.e. 100 documents
3. wait, until few docs are printed
4. turn off printer
5. wait several minutes
6. turn printer on

What is the expected output? What do you see instead?
100 docs are to be printed, but there are less printed docs.

What version of the product are you using? On what operating system?
1.4.9 / Windows 7 (XP)

Please provide any additional information below.
Applet is not looking on printer state and sends jobs to pool.

Original issue reported on code.google.com by vonKer...@gmail.com on 31 Jul 2013 at 11:21

GoogleCodeExporter commented 8 years ago

Thank you for the report.

If you aware of a way to check the printer status via Java prior to printing, 
post a snippet and I'll make a build that checks status prior to printing.

Also, if you can explain exactly how you expect the applet to behave on printer 
power loss, it will shed some light on if this fix is possible or not.

-Tres

Original comment by tres.fin...@gmail.com on 2 Aug 2013 at 4:44

GoogleCodeExporter commented 8 years ago

I'm not a Java-programmer, but how I saw, there is a PrintService attribute, 
called PrinterState. 
(http://docs.oracle.com/javase/7/docs/api/javax/print/attribute/standard/Printer
State.html)

What about behavior, I think an applet could check, if printer status is IDLE 
or PROCESSING before sending print job. (I'm not sure, it's better to test 
before release).

Original comment by vonKer...@gmail.com on 2 Aug 2013 at 8:01

aobag-dev / jzebra

Not all jobs are recieved by printer #146