MouseClick Error

[c1one 0]

Something simple enough, and I am sure it's an oversight, but I have not been able to track this down. The entire script is attached, but here is the point of failure.

Note: I am getting the "Error: subscript used on non-accessible variable" but I thought the initial line of:

AutoItSetOption('MouseCoordMode', 0)

Should address that issue? 

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

; Install updates (minimized and updating for many minutes)
; Updates Not Installed Screen
   ; Wait for updates to complete
WinWait("ProSeries Update")

   ; Wait just over 9 minutes to ensure popup is ready (test alternative to WinWait)
Sleep(550000)

   ; Set focus on Product Licenses window
WinActivate("ProSeries Update")

   ; Send Mouse Click to Install Now button

MouseClick ( "left" [, 581, 362 [, clicks = 1 [, speed = 10]]] )

; end Installing Updates screen

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

 

Thanks for any insights!

c1one

ProSeries2017_No_Customer_Info.au3

[c1one 0]

Udpate, tried with simpler:

 

MouseClick("left", 580, 360, 50)

 

Now, not getting an error, but the installer is not advancing.

Notes: 

1. Verified the Window Information tool was set to "Window" and verified coordinates few times as I moved the window around the screen.

2. Verified I am looking at the mouse tab as well as the position information there.

[careca 278]

Why 50 clicks?

[aa2zz6 24]

I would suggest reading the help file and studying the example they provide for the mouseclick function! ^-^ 

https://www.autoitscript.com/autoit3/docs/functions/MouseClick.htm

[Earthshine 787]

use silent install of installer instead of automation of installer

[c1one 0]

14 hours ago, careca said:

Why 50 clicks?

Just a typo, was copying out of the help file. 

[c1one 0]

3 hours ago, Earthshine said:

use silent install of installer instead of automation of installer

I wish, we typically do that, we have around 500 applications packaged for SCCM, but this is pretty much the only one that has to be done manually, partially because of the updater. 

[Earthshine 787]

you could use the Information Tool to capture the buttons and controls you want to control, and then talk direct to them maybe?

[c1one 0]

1 hour ago, Earthshine said:

you could use the Information Tool to capture the buttons and controls you want to control, and then talk direct to them maybe?

Typically I use:

Send("!N")

or a tab space or tab enter:

Send("{TAB}")
Send("{SPACE}")

But, this installer is a real nightmare. There is no "button" just a giant panel when attempting to get button info with the tool.