Closed GoogleCodeExporter closed 8 years ago
Not a bug. Use the callback qzDonePrinting() as the call is asynchronous and
then use that to make subsequent calls. What you are describing would normally
block the GUI.
We eventually want to queue these requests up but that is harder to manage as
they tend to run off without a good way to track them. That feature is shelved
until after we finish qz-tray.
Original comment by tres.fin...@gmail.com
on 27 Jan 2015 at 3:16
thanks for your reply. but I don't actually get what you mean.
appreciate that if you can give me a simple sample code to achieve my goal.
--simply to print 3 copies of my doc.
Original comment by commute...@gmail.com
on 28 Jan 2015 at 2:07
If you want to append 3 copies, why don't you just append64 3 times? You don't
need to call print each time you append. :)
Original comment by tres.fin...@gmail.com
on 28 Jan 2015 at 9:53
thanks for the hints.
actually in my case, I have 3 rows data returned from jquery. the data are pdf
stream encoded with base64.
when I simply use append64 to append 3 rows, I see only 1 page in my adobe pdf
reader(my printer allows me to spool the print request to a file as well),
though I can see the pdf file size is 3 times comparing with 1 row data.
however 3 copies were printed out.
I think that's a problem for the pdf reader if I simply append 3 rows of data.
but it works fine for me after your hints. thank you very much!
Original comment by commute...@gmail.com
on 29 Jan 2015 at 7:50
Original issue reported on code.google.com by
commute...@gmail.com
on 25 Jan 2015 at 6:03