Christoph Lutz wrote: > Hi, > > I would like to remove the xcu-file > <my_applicationdata>\OpenOffice.org2\user\registry\data\org\openoffice\Office\Commands.xcu > in a programmatic way to ensure, that no user-configuration overwrites the > shared Commands.xcu. Does UNO provide an API to to remove a configuration > ressource from user-space?
No, because this would be a contradiction in itself. If you can set the protection via API you also can remove it this way (with e.g. a macro), but a protection against overwriting should be something you can't bypass. The only working way to prevent modifications on configuration entries by users is by adding the XML attribute 'oor:finalized="true"' to the entry in the "share" layer of the configuration. This still needs some support in the source code so it usually doesn't work for configuration settings that are changed in an interactive way (like e.g. the position of a toolbar), but it works for all settings in the "Options" dialog and - hoorah! - amongst others also for the "Disabled commands" you can specify in the Commands.xcu. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
