We have the following case:
You have an application conntected to LO via UNO. The user then
separately starts a (Start center) window. When he closes it, LO gets
terminated and the external application loses the connection. We want to
prevent thatso that the external application keeps working.
We could use a TerminationVetoException
in the external application to prevent LO from terminating. But this has
the side effect that the user can no longer close the Start center.
Basically we have two options how to fix this:
1. Change the behavior of LO such that the TerminationVetoException
allows closing the last window, but still prevents terminating the
2. Change the behavior of LO such that an open UNO connection counts as
an open window, and the process doesn't get terminated until all
connections are closed.
This option would not need a TerminationVetoException.
Both options do change existing behavior and will possible break
existing applications/workflows out there. So the decision should be
I probably would go for the first one, since the
TerminationVetoException suggests that it will prevent termination. It
shouldn't affect closing a window.
Although I would also consider it as a bug that LO terminates (when
closing a window) while it still has active connections.
Any input on this?
CIB software GmbH
T +49 (40) / 28 48 42 -224
F +49 (40) / 28 48 42 -100
Registergericht München, HRB 123286
Geschäftsführer: Dipl.-Ing. Ulrich Brandner
LibreOffice mailing list