https://bugs.documentfoundation.org/show_bug.cgi?id=168409
--- Comment #5 from Jean-Pierre Ledure <[email protected]> --- (In reply to Michael Weghorn from comment #4) > > Please note that the accessibility UNO API is unpublished and for > LibreOffice-internal use only and subject to change by design. It is not > meant to be used by third party code like macros or extensions, so anything > that relies on it never had any guarantee to keep working. Hmm ... Can you give pointers to that statement ? (https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1accessibility_1_1AccessibleContext.html is silent about such a limitation.) > I'm sorry to say that, but this is an intentional change in the context of > refactoring accessibility code to better fulfill it's actual purpose > (support assistive technology via the platform accessibility protocols) and > increase code maintainability. I understand perfectly your intent. Note however that the release notes also are silent about this API change. > Please try to find an alternative to using the UNO accessibility API - and > feel free to create a new feature request (with clear requirements + use > case) in case you're missing specific API. As a use case, consider next example that ran smoothly in LO 25.2 and before, and aborts in LO 25.8: https://gitlab.com/LibreOfficiant/scriptforge/-/snippets/4874248 The demand is simply: which are the (push)buttons in a toolbar, their coordinates and the commands associated with a click ? Is this stored elsewhere in a UNO instance ? Thanks for helping me to find a workaround. PS: I cannot agree with the actual status (RESOLVED/NOTABUG) of this bug report and feel free to reopen it later if no workaround is feasible. -- You are receiving this mail because: You are the assignee for the bug.
