/officecfg/registry/

/allotropia/zeta-24-2'>distro/allotropia/zeta-24-2 LibreOffice 核心代码仓库文档基金会
summaryrefslogtreecommitdiff
path: root/configmgr/source/winreg.hxx
AgeCommit message (Collapse)Author
2020-01-25tdf#124176: Use pragma once instead of include guardEfdal İncesu
Change-Id: Ifec221d1dbffa3adcc9e3cc7ed13dcf82f1182d7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/87384 Tested-by: Jenkins Reviewed-by: Muhammet Kara <muhammet.kara@collabora.com>
2015-07-14Add HKEY_CURRENT_USER registry integration.Michael Meeks
It seems rather odd that we dump this to a file and parse again to me. Change-Id: Ia32ba9ff3e7878d40032bd7d10fba2c143d11757 Reviewed-on: https://gerrit.libreoffice.org/17033 Reviewed-by: Andras Timar <andras.timar@collabora.com> Tested-by: Andras Timar <andras.timar@collabora.com>
2013-09-10Windows registry configuration backendJanos Farago
The goal is to manage LibreOffice configuration centrally in the enterprise. In Windows Server environment using Group Policies is a common solution for configuration management. Therefore it is required that LibreOffice can read configuration data from Windows registry, too. Windows registry is another configuration layer on the top of normal xml based configuration. For example the following registry setting: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\LibreOffice\org.openoffice.UserProfile\Data\o] "Value"="Example Corp." "Final"=dword:00000001 becomes the following in configuration: <item oor:path="/org.openoffice.UserProfile/Data"> <prop oor:name="o" oor:finalized="true"> <value>Example Corp.</value> </prop> </item> Change-Id: I2cdd83fc93922bf2806417bfd1b83f85cc926d4c Signed-off-by: Stephan Bergmann <sbergman@redhat.com>