https://bugs.documentfoundation.org/show_bug.cgi?id=171924
Alain Romedenne <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |172255 --- Comment #7 from Alain Romedenne <[email protected]> --- > As far as I can tell you can’t run any macros at all from the start center > if you use Tools -> Macros -> Run Macro regardless of whether it uses > XSCRIPTCONTEXT and regardless of what language it’s written in. I think the > problem is that the code decides that script access isn’t allowed for the > start center because the XController for the start center doesn’t support > the XEmbeddedScripts interface (see SfxObjectShell::isScriptAccessAllowed). > Bundled example scripts used to be executable from Tools -> Macros -> Run Macro. If so, this is a regression. > So I guess a simple fix for this would be to implement XEmbeddedScripts in > BackingComp and make it always allow scripting because there’s never a > document in the start center so there’s no reason not to. > Moreover, Python scripts used to be executable from Start Center as further reported in TDF#172255. The origin of such a regression lies between release 6.2.2 and 6.4.5. > This reveals a few other problems that could maybe be filed as separate bugs: > > * If the script isn’t run because scripting isn’t allowed then it should > probably show a dialog box or something instead of just silently doing > nothing. > > * It would probably be better if the code decided whether to allow scripting > based on the location of the script (ie, is it embedded in a document) > rather than depending on what document you happen to be looking at. For > example, if you open a document that contains macros then you can’t run any > macro, even ones that are in your user scripts folder. > > The Organize Macros dialog seems to work better. You can use it from the > start center and it will also let you run macros in your user folder even if > you are looking at a document containing macros. It also seems to stop you > from running macros embedded in the document, but it does it silently. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=172255 [Bug 172255] regression: Unable to use createMessageBox api from Start Center using Python -- You are receiving this mail because: You are the assignee for the bug.
