https://bugs.documentfoundation.org/show_bug.cgi?id=159455
--- Comment #5 from Patrick Traill <[email protected]> --- Users should have no problems if they (or their macro programmers, if different): * Do not use macros at all. * Only use macros to record and replay UI interactions. * Study the release notes carefully. * Have well-run development teams that have set up regression tests for their macros and run them before deploying a new version of LibreOffice. (Atypical?) Problems could mainly be experienced by users who: * Have enough programming experience to find named arguments desirable. * AND Write macros more as a sideline or hobby. * AND Have produced a sufficiently large volume Also by users who: * Use a spreadsheet written by a user such as the above. I have no idea how widespread the use of macros is, so I cannot estimate how many are likely to be affected. My guess is that it is quite likely to affect a very small fraction of users; how small that fraction would be in absolute terms I do not know, but I guess that someone somewhere would get burned. I should like to see this bug fixed too, but I wonder if anything can be done to mitigate the perhaps moderate risk. Obviously there should be a warning in the release notes. An option to enforce old behaviour or one to enable correct behaviour probably adds unwanted complication to the code base. It helps that it would first appear in an early release version used by risk-happy power users. -- You are receiving this mail because: You are the assignee for the bug.
