Autoitscript forum

not having much luck. cant even get this drop down to work. ControlClick("Rental4000 Lease Management (SCL-TSGW01.cube.ad)", "", "[CLASS:RAIL_WINDOW; INSTANCE:2]") Sleep(5000) ControlClick("Rental4000 Lease Management (SCL-TSGW01.cube.ad)","", "", "left", 1, 326, 167) Sleep(5000) ControlClick("Rental4000 Lease Management (SCL-TSGW01.cube.ad)","", "", "left", 1, 891, 202) ;MouseClick("left",726,157) Sleep(5000)

I'm simply running the demo file and getting the below output _WD_Option ==> Success [0] : Parameters: Option=errormsgbox Value=False _WD_Option ==> Success [0] : Parameters: Option=OutputDebug Value=False _WD_UpdateDriver ==> General Error [1 / 2] : DriverCurrent = 152.0.4191.66 : DriverLatest = : $sInstallDir = H:\Quality Assurance\WebDriverUDF\ > UpdateResult = False the relevant edge bit of the demo file Func SetupEdge($bHeadless) _WD_Option('Driver', 'msedgedriver.exe') Local $iPort = _WD_GetFreePort(9515, 9600) If @error Then Return SetError(@error, @extended, 0) _WD_Option('Port', $iPort) _WD_Option('DriverParams', '--port=' & $iPort & ' --verbose --log-path="' & @ScriptDir & '\msedge.log"') Local $sCapabilities = '{"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"excludeSwitches": [ "enable-automation"]}}}}' _WD_CapabilitiesStartup() _WD_CapabilitiesAdd('alwaysMatch', 'msedge') _WD_CapabilitiesAdd('excludeSwitches', 'enable-automation') If $bHeadless Then _WD_CapabilitiesAdd('args', '--headless') _WD_CapabilitiesDump(@ScriptLineNumber) ; dump current Capabilities setting to console - only for testing in this demo Local $sCapabilities = _WD_CapabilitiesGet() Return $sCapabilities EndFunc ;==>SetupEdge the full file is just the demo file #Region - include files ; standard UDF's #include #include #include #include #include #include #include ; non standard UDF's #include "wd_helper.au3" #include "wd_capabilities.au3" #EndRegion - include files #Tidy_Parameters=/tcb=-1

I've been building AutoIt support for Zed , a fast, free, open-source editor for Windows, macOS and Linux. It's now available in Zed's extension registry: open Extensions , search for AutoIt , and install. It uses its own tree-sitter grammar and a native language server written in Rust, so there's nothing extra to install. It picks up AutoIt and SciTE4AutoIt3 installs automatically. What it does Live Au3Check diagnostics as you type. Errors and warnings show up about half a second after you stop typing, without saving. Hover docs for 3,542 functions (built-ins and the standard UDFs): signature, parameters, return value, and a link to the help page. Go to definition and find references across #include d files and the whole project folder. Call hierarchy : see who calls a function and what it calls. Signature help and parameter hints inside function calls, e.g. MsgBox(flag: 0, title: "Hi", ...) . Semantic highlighting : your own functions look different from built-in and UDF ones. Color swatches next to 0xRRGGBB values in GUI color functions, with RGB/BGR handled per function. Quick fixes : add a missing #include for UDF functions, and fix function-name casing. Tidy formatting , #region folding , and an outline with parameters and region contents nested. Bundled tasks : Run, Au3Check, compile with Aut2Exe or the AutoIt3Wrapper GUI, Au3Info, Koda, and kill the running script. 19 snippets for common blocks ( Func , If , For , Switch , #Region , MsgBox , ...). Notes Diagnostics, f

AutoIt Registration-Free COM Manifest Tools A small set of AutoIt utilities for creating, testing, and merging Windows Registration-Free COM manifests. The project is intended to simplify working with native COM DLLs that normally require system registration through regsvr32.exe . FULL INFO: Spoiler AutoIt Registration-Free COM Manifest Tools A small set of AutoIt utilities for creating, testing, and merging Windows Registration-Free COM manifests. The project is intended to simplify working with native COM DLLs that normally require system registration through regsvr32.exe . Included files ManifestCreator.au3 Creates a Registration-Free COM manifest for a selected COM DLL, discovers all COM classes registered by that DLL, and generates a matching AutoIt test script. The tool: Determines the target architecture from #AutoIt3Wrapper_UseX64 . Verifies that the current AutoIt process uses the expected architecture. Prompts for: the COM DLL, an optional ProgID. Temporarily registers the DLL with regsvr32.exe . Discovers every HKCR\CLSID registration whose InprocServer32 points to the selected DLL. Selects one discovered ProgID as the generated runtime test class and creates that COM object. Uses AutoIt's ObjName() to obtain COM information for the selected test class such as: ProgID, CLSID, IID, associated module path. Verifies that ObjName(..., $OBJ_FILE) points to exactly the DLL selected by the user. Collects the ProgID, CLSID, description, ThreadingModel, TypeLib GUID and Typ

Markdown.au3 — an AutoIt UDF for converting Markdown text to RTF . It supports headings, bold and italic text, lists, blockquotes, links, code blocks, and other common Markdown elements. It also provides _MarkdownToRTF_MsgBox() , an enhanced MsgBox() -style dialog that displays formatted Markdown content as RTF. Markdown_Example.au3 — demonstrates Markdown → RTF conversion, displaying the result in a RichEdit control, example AutoIt, SQL, and JavaScript code blocks, and the use of _MarkdownToRTF_MsgBox() . Markdown.zip

Any feedback on the code is appreciated. It compiles and runs so from that perspective no issues but still complex to understand when to use vtable or just hack by knowing the function numbers. no tesseract or other OCR libraries needed, just plain AutoIt and Windows libraries (on windows 11) So once in a while I still use AutoIt and now found out with Powershell 5.1 the WinRt on how to do stuff with the nice OCR gettext (thats also in Win11 Capture tool) and was wondering how to get this working in AutoIt Jumping back and forward in threads of this forum on AutoItObject, ObjCreateInterface, Com/Com++, Embedding .NET in AutoIt, CuiAutomation I already understand WinRt is another animal to get into AutoIt. I didnt want to hijack: Learning step 1 Understanding combase.dll and RoGetActivationFactory Made a very nice script that goes from Learning WinRt To understand the WinRt OCR To highlighting aspects of the rectangles found So much easier with AI then when I wrote the IUIAutomation library (took me months, now only several hours to understand the WinRt base as extension on traditional COM) ; ===================================================================================== ; WINRT OCR SCRIPT - THE BULLETPROOF HYBRID METHOD ; ===================================================================================== #include "ScreenCapture.au3" #region --- GLOBALS & DLLS --- Global $hDLLComBase = DllOpen("combase.dll") Global $hDLLOle32 = DllOpen("ole32.dll") Global $hDLLShcore =

..where did I put that code I had... somewhere 🤷‍♂️

Does the webdriver still work? Just tried launching and I get this console output and screenshot(attached pic). Chrome does not launch. _WD_Option ==> Success [0] : Parameters: Option=Port Value=9515 _WD_Option ==> Success [0] : Parameters: Option=DriverParams Value=--log-path="H:\Quality Assurance\AutoIT Scripts\Know Your Client\Framework\chrome.log" _WD_GetFreePort ==> Success [0 / 9515] : Parameters: MinPort=9515 MaxPort=Default _WD_IsLatestRelease ==> Success [0] : True _WD_Startup: OS: WIN_11 X64 26200 _WD_Startup: AutoIt: 3.3.16.0 _WD_Startup: Webdriver UDF: 1.5.0 (Up to date) _WD_Startup: WinHTTP: 1.6.4.2 _WD_Startup: Driver: H:\\Quality Assurance\\WebDriverUDF\\chromedriver.exe (64 Bit) _WD_Startup: Params: --log-path="H:\Quality Assurance\AutoIT Scripts\Know Your Client\Framework\chrome.log" _WD_Startup: Port: 9515 _WD_Startup: Command: "H:\\Quality Assurance\\WebDriverUDF\\chromedriver.exe" --log-path="H:\Quality Assurance\AutoIT Scripts\Know Your Client\Framework\chrome.log" _WD_Startup ==> Success [0] __WD_Post ==> Send / Recv error [6] : HTTP status = 0 _WD_CreateSession ==> Webdriver Exception [10] __WD_Delete ==> Send / Recv error [6] : HTTP status = 0 _WD_DeleteSession ==> Webdriver Exception [10] : Error occurs when trying to delete session >Exit code: 0 My script is below. It's a bit complex as I create a GUI to be ran but essentially the only function ran once the Chrome driver is launched is _WD_Navigate($sSession, 'www.google.com/') I'm using the chrome.e

Hello, I do hope that I have titled this query correctly? I have the following script that confirms the modified dates of a number of data files - implementing FileGetTime. However, each item is being displayed "one-after-the-other". What I require is a complete file listing! Here is the script: Spoiler ; ----------------------------------------------- ; 9/8/2026 11:55:44 AM ; ----------------------------------------------- #include "ExtMsgBox.au3" #include ; ----------------------------------------------- Opt("MustDeclareVars", 1) ;~ Opt("MouseCoordMode", 0) ; ----------------------------------------------- Global $iEMBWidth = 1000 Global $iMsgDelay = 2 ; --------------------- Global $sAC_DAPath = "D:\App_Config\Digital_Audio" Global $sMainBUPath = "E:\Backups" ; ----------------------------------------------- DrvGBU() ; ----------------------------------------------- Func DrvGBU() DriveGBU() ConfirmFileDates() EndFunc ;==>DrvGBU ; ----------------------------------------------- Func DriveGBU() Local $sSrcDataPath, $sDstDataPath, $sResult = "" Local $aSrcData[] = [ _ "G:\CHT_Files", _ "G:\ControlTrack_Data", _ "G:\F-Key_Data", _ "G:\Mix_Templates", _ "G:\Prf_Data", _ "G:\Scene_Data", _ "G:\Session_Data", _ "G:\Session_Master"] ; --------------------- Local $aDstData[] = [ _ $sMainBUPath & "\App_Config\DriveG\CHT_Files", _ $sMainBUPath & "\App_Config\DriveG\ControlTrack_Data", _ $sMainBUPath & "\App_Config\DriveG\F-Key_Data", _ $sMainBUPath & "\App_Config\DriveG\Mix_Templates

Hello, When i open the Script Editor and press a random keyboard button it instantly closed the editor without Error. i can do line but when i want to write something in it it instantly closed. How can i fix this? Greeting Levi

Hello. I just had to do a minor adjustment to a script a couple of years old and found this difference: With Autoit 3.3.16.0 it was fine to use "" to specify same widht and hide with cell realtive operations: Opt("guicoordmode",2) ; cell relative for $i = 2 to $a2Buttons[0][0] $a2Buttons[$i][0]=GUICtrlCreateButton("Undefiniert - " & $i,-1,5,"","",$BS_LEFT) GUICtrlSetFont(-1,8.5,$fw_dontcare,$gui_fontnormal,"courier new") GUICtrlSetState(-1,$gui_hide) Next With Autoit 3.3.18.0 the relative buttons don't show up, until the "" is replaced with either "default", or a valid value or variable. After these years of course I do not remember anymore, where I picked this "" from to "use same values as before". Perhaps this more strict behaviour could be added here? https://www.autoitscript.com/autoit3/docs/script_breaking_changes.htm cu, Rudi.

I have been having significant issues showing tooltips on toolbar buttons. For example, if I run the _GUICtrlToolbar_SetToolTips example 10 times, the tooltips work maybe 1 or 2 times out of 10 runs. Sometimes no tooltips show at all Sometimes the tooltips show blank Sometimes the tooltips only show a border Sometimes the tooltips text shows but off-center on the tooltip Sometimes (rarely) the tooltips show properly I have tried responding to $TTN_GETDISPINFOW (like the help file example) and I've also tried $TBN_GETINFOTIPW which also works but suffers the same failure rate. Some online help suggests "Stack-Allocated Buffer Lifetime" and memory related issues for the tooltip text but that is all beyond my understanding. I've also tried forcing AutoIt to run as x86 hoping that it might narrow down the issue but it also failed in the same way. Does anyone know more about why this only works 10-20% of the time? Thank you.