# Steps to reproduce 1. Open lowriter or localc 2. Go to Tools → Macros → Organize Macros → Python… ## Expected In the new window the "Create" button should be active, so a user can create a macro. ## Actual "Create" button is grayed out. # Additional information This looks very bad: there's at least a question on StackOverflow about it with 21k views https://stackoverflow.com/questions/21413664/how-to-run-python-macros-in-libreoffice
issue seems to be inherited from OpenOfffice
Konstantin, unfortunately for using Python macroses in LO, you shoud install APSO extension https://extensions.libreoffice.org/extensions/apso-alternative-script-organizer-for-python
(In reply to Roman Kuznetsov from comment #2) > Konstantin, unfortunately for using Python macroses in LO, you shoud install > APSO extension > https://extensions.libreoffice.org/extensions/apso-alternative-script- > organizer-for-python Thanks, so, for this menu to work this extension needs to be shipped with LO out-of-the-box then?
Xisco/Heiko: from UI point of view, if Python macro isn't provided out-of-the-box, shouldn't Python menu entry be removed by default? Indeed an extension can add an entry and at least we wouldn't have a disabled button by default. I had also searched how to use this feature and had given up.
Vast majority of systems has Python installed. Please, just distribute the extension necessary to make it work by default. The extension doesn't weight too much, or does it?
(In reply to Julien Nabet from comment #4) > if Python macro isn't provided... shouldn't Python menu entry be removed You still can _Run_ the macro. Or edit. So hiding the entry makes no sense to me. I would rather not distinguish between the languages at the menu and have Run, Edit (could also be started from the Organize dialog), and Organize there. And at the Run/Organize dialog we could have a filter for the different types.
(In reply to Heiko Tietze from comment #6) > (In reply to Julien Nabet from comment #4) > > if Python macro isn't provided... shouldn't Python menu entry be removed > ... > I would rather not distinguish between the languages at the menu and have > Run, Edit (could also be started from the Organize dialog), and Organize > there. And at the Run/Organize dialog we could have a filter for the > different types. Sorry, I meant removing "Create" button in Python part. (Also, it astonishes me that we embed rhino for Javascript macro + beanshell and nothing for Python but that's another story).
This is not a bug, but I agree to make this an enhancenent request. To write python macros, one must manually create this .py files with your text editor and place it in the required location. This is well documented, see: https://help.libreoffice.org/6.4/en-US/text/sbasic/python/main0000.html I suggest, when clicking on the create button, the user be directed to the help page, or to a popup dialog explaining how to create a python macro. I think it's the basic skills that one understand these explanation when one can write macros in python. APSO is great, but in my opinion a lot of improvements should be made before it can be bundled as default.
Created attachment 174130 [details] Tools Macros Proposed Menu
(In reply to Heiko Tietze from comment #6) > I would rather not distinguish between the languages at the menu and have > Run, Edit (could also be started from the Organize dialog), and Organize > there. And at the Run/Organize dialog we could have a filter for the > different types. Yes, totally agree. See Tools Macros Proposed Menu in comment above. (In reply to Kevin Suo from comment #8) > To write > python macros, one must manually create this .py files with your text editor > and place it in the required location. This is well documented, see: > https://help.libreoffice.org/6.4/en-US/text/sbasic/python/main0000.html > ... > APSO is great, but in my opinion a lot of improvements should be made before > it can be bundled as default. Get real, those are 20th-century instructions. Users expect an IDE. APSO is a nice simple implementation requiring NO improvements to be better than what is provided. The complexity for users to write a simple python macro is an enormous challenge a good interface would help overcome.
Some context: https://superuser.com/q/1297120/514126 If I go to Tools > Macros > Organize macros... > Python, the options for creating new macros are grayed out. After digging a bit on the internet, I discovered that apparently LibreOffice (well, actually upstream OpenOffice) doesn't have its own Python IDE "yet", so they just put a grayed out button in the UI with no explanation as a placeholder. I say "yet" in quotes because I found people complaining about this in 2012 just to be told that it will be fixed any day now.
Can't help here=>uncc myself.
If we some day will decide to rework the macro dialogs as I wrote in bug 120658 it will fix this problem too I think, because we will have only one dialog for all supported script languages
Dear Konstantin Kharlamov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still a problem in 24.8.4.2 Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: 480(Build:2) CPU threads: 12; OS: Linux 6.12; UI render: default; VCL: kf6 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 24.8.4-2 Calc: threaded
Closed as Dupe of bug 56289. Jim is trying right now to do something in this area https://gerrit.libreoffice.org/c/core/+/180476 *** This bug has been marked as a duplicate of bug 56289 ***