Description: Make a new Macro Manager dialog non experimental and enabled by default After a great Jim's work we haveonly one Macro Manager dialog instead current FIVE, but it's still marked as experimental feature I suggest to make a new Macro Manager dialog non experimental and enabled it by default Other old macro dialogs menu items for Basic, Python, JS and Beanshell can be just hidden and only if the new Macro Manager dialog will be good for all QA and other people we can delete the old code and UI files. I suggest it because we have time now for testing before 26.2 release and I don't want Jim's great work be just without using Steps to Reproduce: - Actual Results: We still have a new Macro Manager as experimental feature Expected Results: We have a new Macro Manager as default ONE dialog for macro management and can test it deeper Reproducible: Always User Profile Reset: No Additional Info: current 26.2 master build
The link to the patch with implementation https://gerrit.libreoffice.org/c/core/+/176254
The Macro Manager is available since 25.2 * enable Experimental Features * launch the dialog per Tools > Macros > Macro Manager... The proposal is to a) make the command .uno:MacroManager non-experimental b) remove the Organize Macro menu .uno:ScriptOrganizer along with the items (Basic, Python, Javascript, Beanshell) .uno:MacroOrganizer (and the related dialog/s)
From the commit: > Known issues: > + Scripting framework library rename for BeanShell, Java, and JavaScript > always returns fail when there are no macro entries in the library even > though it actually succeeds. The same thing happens using > SvxScriptOrgDialog::renameEntry. > + Deleting Basic macros from the Macro Manager dialog is not implemented yet. Are these issues fixed meanwhile? If not, are they tracked anywhere? Are there workarounds?