Hi Matthias,

>> I have following problem. I wrote a little program that converts
>> documents in background, without showing a user interface. If I have an
>> active OO screen and close this, my conversion utility crashes.
>>
>> My questing: how can I stop OO closing my conversion tool?

> OOo currently doesn't manage its lifetime correctly in presence of
> connections using hidden taks ATM so you have to take care for this by
> yourself. The best way is to implement a terminate listener, register it
> at the desktop service and don't allow to terminate the application
> until you are done. The drawback is that after you are done you have to
> check wether there are any tasks at the desktop and if not you have to
> call terminate() at the desktop. Otherwise OOo will stay in memory even
> if no visible task exists anymore.

That seems for me a really good solution. In case I want a "OO
Quickstarter" to remain alive after finishing my conversion I don't have
to check for other tasks and don't call terminate() - I just have to
close my document. Is that correct?

> We hope to make this more "automagical" in the near future. OOo
> shouldn't terminate as long as any external connection exists.

That would be great! Is there a possibility to vote for this?

Greetings, Tobias

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

Reply via email to