IMHO, it is simply asking for trouble to use the same UserInstallation
(same LO instance) for both some 3rd-party application that uses LO, and
for interactive use.
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
Am 20.09.2016 um 11:56 schrieb Stephan Bergmann:
On 09/20/2016 08:30 AM, Samuel Mehrbrodt wrote:
Am 19.09.2016 um 17:29 schrieb Stephan Bergmann:
On 09/19/2016 05:17 PM, Samuel Mehrbrodt wrote:
It turned out we need to implement both. The first option was fine when
only closing the window -
On 09/20/2016 08:30 AM, Samuel Mehrbrodt wrote:
Am 19.09.2016 um 17:29 schrieb Stephan Bergmann:
On 09/19/2016 05:17 PM, Samuel Mehrbrodt wrote:
It turned out we need to implement both. The first option was fine when
only closing the window - but we also want to be able to close the
visible
Hi Tor,
I'm not aware of any impacts on the --headless, --invisible and --quickstart
options.
When starting with --headless or --invisible, you are not able to start any
visible frame afterwards.
Something similiar as my patches do could be achieved by using --quickstart.
The difference is
How does this interact with the options --headless, --invisible, and
--quickstart ? Could the same end result be achieved by starting
LibreOffice with one of them?
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
Am 19.09.2016 um 17:29 schrieb Stephan Bergmann:
On 09/19/2016 05:17 PM, Samuel Mehrbrodt wrote:
It turned out we need to implement both. The first option was fine when
only closing the window - but we also want to be able to close the
visible frames with "File->Exit" while keeping the process
On 09/19/2016 05:17 PM, Samuel Mehrbrodt wrote:
It turned out we need to implement both. The first option was fine when
only closing the window - but we also want to be able to close the
visible frames with "File->Exit" while keeping the process running.
Do we? I think there is probably a
I went with the first option and created this patch:
https://gerrit.libreoffice.org/#/c/29018
It turned out we need to implement both. The first option was fine when only
closing the window - but we also want to be able to close the visible frames
with "File->Exit" while keeping the process
Hi Stephan, *
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
On 09/16/2016 03:39 PM, Samuel Mehrbrodt wrote:
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
10 matches
Mail list logo
