Fix macro security UI usability problems

* Don't hide the option dialogs "Macro security" push button.
  I don't see any reason, why these settings should be hidden, if
  macros are disabled or settings locked. At least a user can now
  check, what is going on (still nothing shows disabled macros for
  a document in the UI AFAIK).
* Don't scale the lock icons of the trusted list boxes.
  This just uses the same alignments, which the macro security
  level lock image uses, otherwise the image is scaled to fit the
  whole space of its layout cell.
* Don't disable the trusted list boxes.
  If the setting is locked, it's sufficient to disable all the
  buttons, which allow modification (so View can stay enabled).
  This way you can still scroll the list. Correct button handling
  is already implemented and works for me.
* Catch exceptions of broken certificate data.
  If your config contains certificates, which can't be correctly
  decoded, the NSS backend will throw an exception, which kills
  the dialog, but not the nested loop, resulting in a locked LO.
  Also show an error dialog with the broken base64-encoded data.

Change-Id: I79002e0ce85cf9a9017caf858407f2f635a3a074
Reviewed-on: https://gerrit.libreoffice.org/85056
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
(cherry picked from commit b3348ce498b3d54b3e5e6518954ad9d5e917b8f2)
Reviewed-on: https://gerrit.libreoffice.org/85282

1 files changed, 0 insertions, 14 deletions

diff --git a/cui/source/options/optinet2.cxx b/cui/source/options/optinet2.cxx
index b79a1d9bbd3e..5e3c6a878ff4 100644
--- a/cui/source/options/optinet2.cxx
+++ b/cui/source/options/optinet2.cxx
@@ -734,20 +734,6 @@ IMPL_LINK_NOARG(SvxSecurityTabPage, MacroSecPBHdl, weld::Button&, void)
 
 void SvxSecurityTabPage::InitControls()
 {
-    // Hide all controls which belong to the macro security button in case the macro
-    // security settings managed by the macro security dialog opened via the button
-    // are all readonly or if the macros are disabled in general.
-    // @@@ Better would be to query the dialog whether it is 'useful' or not. Exposing
-    //     macro security dialog implementations here, which is bad.
-    if (    mpSecOptions->IsMacroDisabled()
-         || (    mpSecOptions->IsReadOnly( SvtSecurityOptions::EOption::MacroSecLevel )
-              && mpSecOptions->IsReadOnly( SvtSecurityOptions::EOption::MacroTrustedAuthors )
-              && mpSecOptions->IsReadOnly( SvtSecurityOptions::EOption::SecureUrls ) ) )
-    {
-        //Hide these
-        m_xMacroSecFrame->hide();
-    }
-
 #ifndef UNX
     m_xCertFrame->hide();
 #endif