Therefore, finally, the way to click the button in a more satisfactory way than hitting the return key looks like this: tell application 'System Events' to tell process 'System Preferences' ¬ Which reveals it has one action available, AXPress (this is equivalent to a mouse click). Now run this command: get the actions of button 'OK' of sheet 1 of window 'Built-in Retina Display' You'll be able to see that its description is merely 'button', which isn't what you had hoped. However, we do know its name and that there's only one of it, so we can reference it by name directly.Īs a side-bar, if you quickly run this command: get the properties of button 'OK' of sheet 1 of window 'Built-in Retina Display' You can use the whose filter to target it instead, which would be done like this (via System Events and the System Preferences process): get buttons of sheet 1 of window 1 whose name is 'OK'īut all this does is ask AppleScript to search for a button whose name we know, then annoyingly give the result back to us as a list (the list structure can be flattened by requesting the first button of sheet 1.). To get button 'OK' of sheet 1 of window 'Built-in Retina Display' The 'OK' button is referenced like so: tell application 'System Events' to tell process 'System Preferences' ¬ Regarding identification of UI elements within the GUI objects hierarchy, you got the class of the button in question wrong as well as its description. The drawback is that the preference pane has tone in focus, and if it loses focus before it receives the keystroke, the rest of the script will fail. It's quick, simple, and saves the hassle of identifying UI elements within the hierarchy.

Since you're using System Events anyway, and the button in question is selected by default (indicated by being highlighted in blue), just make sure that the preference pane is in focus and use System Events to hit the return key: tell application 'System Events' to keystroke return

Applescript tutorials mouse auto click