https://bugs.documentfoundation.org/show_bug.cgi?id=155666
Gabor Kelemen (allotropia) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Gabor Kelemen (allotropia) <[email protected]> --- I took a look at this, and the problem is that you have tested it on a pre-exising install, with an existing instdir/user/registrymodifications.xcu file - which contains a value for this variable. A little advertised detail of LO is that lots of configuration defaults are written to this at the first start of LO, or the first opening+closing of a config dialog that contains these settings. The contents of this file take precedence over factory defaults and admin level customizations. This is explained in detail in these talk slides: http://www.linux-kongress.org/2010/slides/ooo_netzwerk-effenberger.pdf http://www.linuxtag.org/2012/fileadmin/www.linuxtag.org/slides/Thorsten%20Behrens%20-%20LibreOffice%20configuration%20management%20-%20Tools_%20approaches%20and%20best%20practices.p331.pdf http://libreoffice.hu/wp-content/uploads/2014/02/Andras_Timar_LibO_Central_Config_Management-1.pdf Try to close LO and rename your registrymodifications.xcu file - the next start will take the value from your extension. This worked for me, showing that the config snippet is correct. If you also want this to work for all users of your extension, you can try locking it down like this: <prop oor:name="UseSystemFileDialog" oor:finalized="true"> This will force your setting even if there is a pre-existing setting in the user level registrymodifications.xcu -- You are receiving this mail because: You are the assignee for the bug.
