Hi Heiko,
> I wrote a blog post some time ago about how to make a feature optional. It
> comes from a
> non-developer/layman perspective to encourage people to look into the code.
> Perhaps it’s
> a bit helpful.
>
I wrote a blog post some time ago about how to make a feature optional. It
comes from a non-developer/layman perspective to encourage people to look into
the code. Perhaps it’s a bit helpful.
https://design.blog.documentfoundation.org/2018/04/14/easyhacking-how-to-make-a-feature-optional/
>
Hi Michael,
>>> utl::ConfigItem is sort of deprecated and you should have a really good
>>> excuse to use it in new code.
>>
>> I have no better excuse than that it existed in the same component.
>> Which method should I use instead (or where can I find good examples of code
>> to use as
On 31.01.19 11:48, Winfried Donkers wrote:
Therefore I need to add a configuration item to registrymodifications.xcu.
I have created a class to obtain the configuration item, using a derivative of
::com::sun::star::utl::ConfigItem and copying/adapting existing code to
retrieve configuration
Including the mailing list this time...
Winfried
-
Hi Michael, Stephan,
Thank you for your quick responses.
>> Therefore I need to add a configuration item to registrymodifications.xcu.
>> I have created a class to obtain the configuration item, using a derivative
>> of
On 31.01.19 11:00, Winfried Donkers wrote:
Hi,
I am working on an enhancement for Calc, tdf90180.
Therefore I need to add a configuration item to registrymodifications.xcu.
I have created a class to obtain the configuration item, using a derivative of
::com::sun::star::utl::ConfigItem and
On 31/01/2019 11:00, Winfried Donkers wrote:
Therefore I need to add a configuration item to registrymodifications.xcu.
The form of configuration content is defined in .xcs files in
officecfg/registry/schema/, and the configuration data that ships with
LO is defined in .xcu files in
