https://bugs.documentfoundation.org/show_bug.cgi?id=145272
--- Comment #12 from MartinPC <[email protected]> --- EXECUTIVE SUMMARY: I think users who have reported this bug are correct. I have no background in coding/programming and have been trying to iteratively develop LibreOffice BASIC macros with the help of AI. This very frequently involves pasting new blocks of code over older blocks of code in one of my four My Macros & Dialogs.Standard macro modules. Sometimes it involves manually deleting or adding extra blank lines or cutting out an existing macro's code block and pasting it elsewhere, to make it easier for me to understand the modules' structure and navigate it. I am currently working in LibreOffice 26.2.5.2 and have noticed that most of the time after I have performed one or more of the above operations — DEFINITELY after code-pasting and blank-line-deleting operations and POSSIBLY after blank-line-adding operations as well — the File>Save MENU COMMAND GETS UNGRAYED-OUT but the corresponding TOOLBAR ICON DOES NOT. I *believe* but am not 100% certain that if I type actual printable characters into a module (e.g., adding a comment line or changing a subroutine's name), that THAT *does* in fact cause the File>Save toolbar icon to get ungrayed-out. Finally, while I am testing a macro, if I attempt to save module changes by doing menu File>Save while a previous test is still running but paused (and the Run>Stop menu command is ungrayed-out), the File>Save toolbar icon will become ungrayed-out and will *stay* ungrayed-out until the currently active macro is stopped or exited and the changes are saved. Clearly, whatever routines are toggling the File>Save toolbar icon's active/inactive status need to be reviewed and debugged. The practical result in terms of usability is that after a tiring session where I have been jumping back and forth between the macro editor and other application windows, I can't remind myself with a quick glance at the toolbar whether I have unsaved changes in my modules; I have to open the File menu both to remind myself and, if I want to keep the changes, to save them. (Of course I could also do Ctrl+s on the keyboard for a quick save without checking, but regardless, the File>Save icon is not available.) Not being able to see the modules' saved/unsaved status at a glance can also make it easier to accidentally run a second test before new changes have been saved, yielding potentially confusing buggy results that are identical to the previous test run's until I remember to go back and save the changes. This is a relatively minor bug, but it can be confusing and annoying to non-coders like me — who I'm guessing make up a majority of LibreOffice's users. -- You are receiving this mail because: You are the assignee for the bug.
