Description: Add Macro Security Settings button to macro infobar After Samuel's patches we have a nice macro infobar instead old blocker dialog if file contains any macro and we have High macro security level. But the infobar has only one Show Macro button that allows to see macroses in our file, but for macro using we still should open Options dialog, then Security, then Macro security and finally select another security level. Users would be happy if they can open Macro Security dialog faster by button pressing on the infobar at once. I suggest to add Macro Security Settings button to the macro infobar that open Macro Security dialog at once. Steps to Reproduce: - Actual Results: We don't have Macro Security Settings button on the macro infobar Expected Results: We have Macro Security Settings button on the macro infobar Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded
Sounds reasonable. Could be labelled "Options" or better "Macro Security".
I'm not sure this is a good idea. In the default configuration, macros are allowed (but must be confirmed). So this infobar will not be shown in the default configuration. When LO is configured to block macros, as it is often the case in corporate environments, the user is usually not expected or even allowed to change that setting. So I don't think we should display the Macro security settings button in the infobar. If anything, it must be hidden if the macro security settings are locked down (readonly).
Samuel, LO blocks all macro by default, macro security is HIGH by default and user should do many actions for macro enable, therefore I wrote this enhancement
(In reply to Samuel Mehrbrodt (allotropia) from comment #2) > When LO is configured to block macros, as it is often the case in corporate > environments, the user is usually not expected or even allowed to change > that setting. We could disable or better hide the button in this case.