Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I've had trouble working out, from the code, what a user installation path
is.  There are two classes called Bootstrap, and my one reads the details
from a map, which I assume is populated somewhere.

Is there a broad-brush guide to how the code works, for newbies?

James.

On Tue, Jan 3, 2012 at 8:51 PM, Stephan Bergmann <sbergman@redhat.com>wrote:

On 01/03/2012 02:35 AM, James C wrote:

What now strikes me as more likely is:
  - each process from each version of LibreOffice cooperates with
other processes, so that only one LO process is running
  - (probably) the cooperation extends across versions
  - I don't recall whether I got a window, or only a change of current
application
  - I may have had a change to an already-running process from the other
version
  - (probably) closing that to retry enabled me to have the version I
wanted


Yes, that's another source of confusion.  Upon startup, an soffice
instance tries to connect to a "named pipe" with a well-known name (and
sets that pipe up in listening mode if it does not yet exist).  That way,
only one instance will ever be running for a given installation. The
well-known name contains (a hash of) the user installation path, so
whenever two installations would share a user installation, they are
connected in this way.  (See desktop/source/app/**officeipcthread.cxx for
details.)

Stephan


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.