[dev] Re: Dispatcher:
Mathias Bauer nospamformba at gmx.de writes: The only way to find out about the successfull of a printing process is using a PrintJobEventListener. Hi, I have the same problem. I think the issue is not waiting for the print process to finish, but rather waiting for the print dialog to close. Anyone: is this doable? regards, joost -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
[dev] Re: Dispatcher:
On 02.06.2011 01:06, Joost wrote: Mathias Bauernospamformbaat gmx.de writes: The only way to find out about the successfull of a printing process is using a PrintJobEventListener. Hi, I have the same problem. I think the issue is not waiting for the print process to finish, but rather waiting for the print dialog to close. Anyone: is this doable? regards, The event you have to wait for is when the OOo Print Job finishes. This is available for PrintJobEventListeners. The printing process still might take some time, but this is not under control of OOo anyway. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Oracle: http://blogs.sun.com/GullFOSS Please don't reply to nospamfor...@gmx.de. I use it for the OOo lists and only rarely read other mails sent to it. -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
[dev] Re: Dispatcher: \.uno:Print\ wait for print job to finishlocalhost/
Hi Darwin, On 01.03.2011 22:55, Darwin Whaley wrote: Hello, Mathias! I saw your response for this issue (http://www.mail-archive.com/dev@openoffice.org/msg11443.html) while investigating new behavior in OpenOffice.org 3.3. This URL indicates that the uno:print call is no longer synchronous: http://www.oooforum.org/forum/viewtopic.phtml?t=115035 I hoped that passing Asynchron and Boolean.FALSE in the properties object might solve this problem, but it does not. There has been no response to the developer in the above URL. Are you aware of this new behavior, and how applications using the OpenOffice.org API are now supposed to determine if a print job is successful? The new asynchronicity is not introduced by the dispatcher but by the printing process itself. The same could happen to you even before, depending non the operating system and the printer. The only way to find out about the successfull of a printing process is using a PrintJobEventListener. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Oracle: http://blogs.sun.com/GullFOSS Please don't reply to nospamfor...@gmx.de. I use it for the OOo lists and only rarely read other mails sent to it. -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
