https://bugs.documentfoundation.org/show_bug.cgi?id=168409
--- Comment #12 from Jean-Pierre Ledure <[email protected]> --- (In reply to Michael Weghorn from comment #10) > Does this mean you now have a potential alternative to > accessiblecontext = element.RealInterface.AccessibleContext Yes, partially, I can derive the buttons names from the settings > Is the challenge finding the coordinates of a known button in general, or > related to the pushed button in particular? Actually a script receives the X, Y, Width, Height values for any button. However, in se, this info is not very useful. Except when a button is clicked, activates a script, and a popup menu or alike is desired. That's why I proposed in comment#9 to pass to the script a MouseEvent argument. This would be an IMHO acceptable incompatibility between LO releases: easy to explain and to fix in existing scripts. > Do you have any UNO interface (X...) for the underlying button object, or > only some name/text retrieved from the resource associated with the button? > > Since you mention com.sun.star.comp.framework.LayoutManager: Do you possibly > have a com::sun::star::ui::XUIElement reference from which you can retrieve > a com::sun::star::awt::XWindow reference of the corresponding button, or is > only the toolbar available that way? TBC ? > (If you can get an XWindow, XWindow::getPosSize might be helpful to get the > coordinates.) -- You are receiving this mail because: You are the assignee for the bug.
