Re: [api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-12-04 Thread Tobias Krais
Hi Mathias,

 Sounds like a bug to me if the PrintJobListener isn't called in case the
 print failed. Would you mind to create an issue?

I've done so: http://www.openoffice.org/issues/show_bug.cgi?id=72240

I hope this will be fixed soon. Seems to be very serious for me.

Thank you for your help and hints.

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-12-04 Thread Mathias Bauer
Tobias Krais wrote:

 Hi Mathias,
 
 Sounds like a bug to me if the PrintJobListener isn't called in case the
 print failed. Would you mind to create an issue?
 
 I've done so: http://www.openoffice.org/issues/show_bug.cgi?id=72240
 
 I hope this will be fixed soon. Seems to be very serious for me.

I see no problem in getting this fixed in OOo2.2.

Ciao,
Mathias
-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to [EMAIL PROTECTED].
I use it for the OOo lists and only rarely read other mails sent to it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-12-04 Thread Tobias Krais
Hi Mathias,

 I see no problem in getting this fixed in OOo2.2.

I read it. Thank you for your fast work!

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-12-01 Thread Mathias Bauer
Tobias Krais wrote:

 Hi Mathias,
 
 I assume that you can call it a feature; to my knowledge we are not able
 to queue printer requests. Instead of waiting for a fixed time you could
 register a print listener to get notified when printing is done.
 
 I did do before. But if the user wanted to print a non-existing page,
 the printer listener was hanging at the state of job started, but never
 exited. I did not find a workaround for this bug, so I decided to throw
 away the printer listener and to solve it this way.

Sounds like a bug to me if the PrintJobListener isn't called in case the
print failed. Would you mind to create an issue?

Ciao,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to [EMAIL PROTECTED].
I use it for the OOo lists and only rarely read other mails sent to it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-11-30 Thread Tobias Krais
Hi together,

I wrote a little program and wonder about its behaviour. This java
programm first sets the printer, then the printer tray and prints
afterwards the pages I want. Printing is started with:
xPrintable.print(printOpts)

Then my programm continues to set another printer tray, the same printer
and prints some other pages with:
xPrintable.print(printOpts)

Now something interesting happens: the second print request is just
ignored! I can solve this problem by telling my programm to sleep for
about 2 seconds after the first print is started and then continue with
the second print.

Is this a bug or a feature?

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] Bug?!: xPrintable.print(printOpts) is too slow for itself

2006-11-30 Thread Tobias Krais
Hi Mathias,

 I assume that you can call it a feature; to my knowledge we are not able
 to queue printer requests. Instead of waiting for a fixed time you could
 register a print listener to get notified when printing is done.

I did do before. But if the user wanted to print a non-existing page,
the printer listener was hanging at the state of job started, but never
exited. I did not find a workaround for this bug, so I decided to throw
away the printer listener and to solve it this way.

Greetings, Tobias

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]