Hi,
Frank Schönheit - Sun Microsystems Germany schrieb:
I would also be interested in changing RestrictedPath from an environmental
variable to a configuration (.xcs/.xcu) setting. Is there a specific reason
an environment variable was chosen over a configuration setting?
The idea was to have a feature which prevents users from changing the
respective setting. Nowadays, where the configuration supports locking
settings into "readonly" state, probably nothing is to say against
making this a configuration setting.
So how was that supposed to be used? I assume that would be by editing
the soffice script to set that variable before invoking soffice.bin?
(Otherwise a user could always overwrite an environment variable just as
easily.) Not well suited for Windows use then, where there is no
existing script ....
How could
changing to a configuration setting be done without adversely affecting
existing users -- use the configuration value if it is set, otherwise look
to the environment variable?
The order probably doesn't matter, but something like this, yes.
The most correct would be to use a configuration value with no default,
which means you get a NIL value (a VOID Any in UNO) when reading. Then
you could have
VOID -> look at environment
Non NIL -> Use the value
If the setting is a list of pathes or URLs, the best value type would be
string-list (Sequence< String> in UNO) . Note that an empty string-list
is distinct from NIL.
The one thing this doesn't permit, is using an empty string-list to
signify NO allowed folders.
HTH, Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
