|
Well... only that ideally, the macro that should know the name of the button is the one bound in Clique. My "/click" macro could have many conditionals to choose what button to click, after all, and assuming that I also want to trigger my message when I actually click on the button with my mouse (which means that I indeed show this message with a GetMouseFocus() or something), I could have situations where:
- My mouse is over Frame1
- I simulate a click on Frame2
=> I get a message about Frame1 and another message about Frame2, while nothing happened to Frame1
|