Leaderboard

@bobbiehansen CodeCrypter may be of help.

Draksyl, The "process and lifecycle" for releases is whenever Jon has some time to spend on development - which as he has to work to keep a roof over his head and food on the table is not as frequent as some more impatient users might wish! To the best of my knowledge there is no standard set of tests against which new versions are run. We do try our best to avoid problems but a quick look at the development history of AutoIt shows that major releases are nearly always followed in reasonably short order by updates to fix problems that have been caused - most often in the UDFs that come with the standard install. As you stated, the AutoIt license states that the software is 'provided "as is" without warranty of any kind' so it is very much up to you to determine if the product is "fit for purpose". Having been involved in the aeronautical world all my life (operator rather then designer) I understand your problem - sorry we cannot be any more helpful. M23

Fine by me - its not my money 😉

I worked for an IT multi-national enterprise for many years. And there is no simple technical solution to avoid 100% unauthorized usage of software without a backlash to help desk. They finally choose to have a trustworthy relationship with their customers. In other words, don't sell your stuff to companies with doubtful history.

Added this UDF the wiki 🙂

What about this? ;Coded by UEZ build 2023-10-30 ConsoleWrite(Hex(RGB(255,0,0)) & @CRLF) ConsoleWrite(Hex(ARGB(128,80,120,240)) & @CRLF) Func RGB($r, $g, $b) Return BitOR(BitShift(Max(0, Min(255, $r)), -16), BitShift(Max(0, Min(255, $g)), -8), Int(Max(0, Min(255, $b)))) EndFunc Func ARGB($a, $r, $g, $b) Return BitOR(BitShift(Max(0, Min(255, $a)), -24), BitShift(Max(0, Min(255, $r)), -16), BitShift(Max(0, Min(255, $g)), -8), Int(Max(0, Min(255, $b)))) EndFunc Func Min($a, $b) Return $a < $b ? $a : $b EndFunc Func Max($a, $b) Return $a > $b ? $a : $b EndFunc

This should be easy with the correct xpath -- $sElement = _WD_FindElement($sSession,$_WD_LOCATOR_ByXPath,"//div[150]") _WD_ElementAction($sSession, $sElement, 'click')

Btw. There is always a better way to determine the correct XPath / CSSQuery. Please share the link to website or at least use browser extensions like SavePage WE to save website to single MHTML file, anonymyze the MHTML fle content and share to us.

Did you already look at _WD_GetElementByRegEx() ?

#include <Array.au3> Local $aData = StringSplit("i want to click the one at the index of 150", "") ;~ _ArrayDisplay($aData) ;case if i know that is in line 15 Local $Ln = 15 ConsoleWrite($aData[$Ln] & " if i know that is in line " & $Ln & @CRLF) ;case I don't know the line For $i = 1 To $aData[0] If $aData[$i] = "k" Then ConsoleWrite($aData[$i] & " found in line " & $i & @CRLF) ExitLoop ; if it finds it, it can exit the loop, you don't need it to go all the way EndIf Next Edit: If(x==150) then == is not the correct expression here, (a waste of time) == Tests if two strings are equal. Case-sensitive. The left and right values are converted to strings if they are not strings already.