Leaderboard

...found the gif...

The latest version of AutoIt includes some groundbreaking features, among others it is now armed with Artificial Intelligence. Whenever a user launches an .au3 file that does not comply with Forum Rules, Human Rights or a healthy lifestyle, the execution is prevented. For example, if you order a pepperoni pizza and your health scores are poor, you'll get the broccoli one . Seriously, what kind of help do you expect without posting at least one of the scripts.

Most likely there is somewhere another modal dialog around (or a 2nd desktop?) that prevents you from activating something else and that modal goes away as when you click the desktop Hard to say but I would suggest for debugging * use controlxx functions * add a winactivate for the desktop to first activate the desktop (below by using shell application) $oShell = ObjCreate("Shell.Application") $oShell.ToggleDesktop() or probably winactivate("[classname:#32769]","") * See what winmove is doing with your window * Use winlist to dump all titles that are on screen * Loop through winlist items and set them all 1 by 1 active and see whats happening (offcourse for debugging) * Alternative: Get your window x,y position and move the mouse and click (this assumes its on foreground) https://www.autoitscript.com/autoit3/docs/functions/MouseMove.htm https://www.autoitscript.com/autoit3/docs/functions/MouseClick.htm

.... and that is assuming there really is an .x. as second octet!

#1 should be : If $dGateway2 = "10.x.1.1" OR $dGateway2 = "10.x.2.1" THEN $ImageServer = "Server1" ElseIf.... #2 should work #3 should be : Select Case StringStripWS($dGateway2, 8) = "10.x.1.1" $ImageServer = "Server1" Case....

As workaround try to use ControlSend() instead of Send() if possible.

Then @Nineshould be awarded the solution

One important thing to remember is that most (all?) Webdriver implementations only support xpath 1.0. Some of the information you find on the web may not apply as it is geared towards xpath 2.0 / 3.0. Have you tried writing the xpath like this? $sElement = _WD_FindElement($sSession, $_WD_LOCATOR_ByXPath, "//tr[@data-location='abc']/td/span[@class='456']")

Just repeat with the next value : _Excel_RangeWrite($oWorkbook, $oWorkbook.Activesheet, $vin, "B" & $NextRow) If @error Then MsgBox(0, "Error", "Writing vin") Continue with the third, etc. You could also stock the data into an array instead of individual variables, and write the whole array at once starting at column A

Then use : _Excel_RangeWrite($oWorkbook, $oWorkbook.Activesheet, $c_number, "A" & $NextRow) If @error Then MsgBox(0, "Error", "Writing c_number") Adding error handling is very much recommended

Local $NextRow = $oWorkbook.ActiveSheet.Usedrange.Rows.Count + 1 That will provide you the next free row.

Have you tried to use ControlGetText ? Instead of MouseClick / Send / Sleep, you could get the data with a single statement. Use Au3Info.exe tool to get control information from your source application.

Sounds like a bad HDMI cable, try upgrading the firmware.

From evil

Your updated version not only fixed the problem but is much cleaner and elegant. So the OP can learn how good code looks like in addition. Every post that solves the OPs problem should be a candidate to be marked by the OP as "Solution".

Unfortunately, it seems not possible to mark more than one post as "Solution" .

So finally I clean up it a little, changed function names, add function headers, and here they are: ;~ Core functions: _WD_CapabilitiesStartup() _WD_CapabilitiesAdd() _WD_CapabilitiesGet() ;~ Internal functions: __WD_CapabilitiesInitialize() __WD_CapabilitiesSwitch() __WD_CapabilitiesNotation() ;~ Helper functions: _WD_CapabilitiesDump() _WD_CapabilitiesDisplay() Check the attached version. Does it work for you? Do you have any questions at this stage? In your opinion, does this version deserve an official release? (of course, after separating the examples).

Just my 2 cents worth. Somewhere in this thread you say that your WD Capabilities UDF should become part of the WebDriver UDF. In this case, I would strongly recommend using the WebDriver UDF naming convention. The main benefit would be not to confuse users.