Yeah, sorry ... I've been playing with the UIAutomation script version of this and don't want to write documentation for this version because the new one is so different.
First off: I HIGHLY recommend avoiding clicks for UI Automation. They're unreliable because they have to have coordinates. Some windows won't respond to a click at 0,0 so you have to specify coordinates just to get them to work at all.
The problem you're having has to do with which element you're targeting and the exact coordinates being clicked. Send-Click
targets the specific window/control that has been selected, and defaults to the 0, 0 coordinates, so your click is basically hitting the window border where nothing happens when you click or double-click.
The following works:
$edit= Select-Window notepad | Select-Control Edit
$edit | Send-Keys "This is a test of the clickity-click system"$edit | Send-Click -DoubleClick -top 10 -Left 10
The click selects the first word. It works because the click is going
to the Edit control,
and is offset at 10, 10 from the top left corner of the window. If you don't offset, the click goes to the border of the edit control, which
still doesn't do anything. My guess is that in your example, 800, 425 is too far and going right off the window, but probably wouldn't work without targeting the edit control anyway.
But again, I wouldn't use clicks if I can avoid it. Send the keystrokes or move-window, etc when you can.
I am currently working on a Module Packaging system for PoshCode.org, but when that's finished, I will prioritize getting the next version of the
UI Automation script version of WASP