Leaderboard

Hi AutoIters! Here is my new UDF about GUIs: it's an enhanced mixture of Advanced InputBox (deprecated) and KODA Parser (deprecated), with additional functions. What you can do with it: Parse KODA files and directly create GUIs (_GUIUtils_CreateFromKODA) Parse a simple JSON form definition to simply create advanced InputBoxes with any amount/type of input controls (_GUIUtils_CreateFromJSON) Created GUIs are returned as Scripting.Dictionary objects, and you have helper functions to access GUIs controls by their names (_GUIUtils_HWnd, _GUIUtils_CtrlID, _GUIUtils_HCtrl ...) A function that can make a GUI created from KODA/JSON (defined by it's $oForm object) and make it a modal InputDialogBox (just like InputBox, but returns all entered data as Scripting.Dictionary object) Functions are documented, and there are some examples. Consider this UDF as beta, but since I'm currently using it in a small commercial project, it should become production ready in near future. To always get the latest code version, get it from Github (more up to date than this topic). Update 04/02/2020: New simple application example Fixed focused control handling in _GUIUtils_InputDialog Reset input values before returning from _GUIUtils_InputDialog Fixed CloseOnEsc in _GUIUtils_InputDialog Fixed Input not reset Fixed all ListBox items are selected Project now on GitHub https://github.com/matwachich/autoit-guiutils/ Update 05/02/2020: Support for nodate for Date and Time input controls (pass null value) New handling of focused control _GUIUtils_InputDialog: Now, you can specify the focused control in $oInitialData by setting "controlName:focus" = True Updated documentation of _GUIUtils_InputDialog Update 07/02/2020: Bug corrected when setting Data input control Added: abillity to read a single input control New functions (_GUIUtils_GetInputs, _GUIUtils_WriteInputs), documentation completion. Readme file and screenshots on Github Page GUIUtils.zip

Sorry. My bad, I didn't provide explanations What my code does is : from a "test.txt" file containing this red station - 192.168.1.10 yellow station - 192.168.1.11 It first builds a "test.ini" file which content is [stations] red station=192.168.1.10 yellow station=192.168.1.11 Then using the IniReadSection function you can directly get a 2D array to use in the script #Include <Array.au3> #include <GUIConstants.au3> ; create the ini (for the example) $newtext = "[stations]" & @crlf & StringReplace(FileRead("test.txt"), " - ", "=") FileWrite("test.ini", $newtext) ; read to a 2D array $res = IniReadSection("test.ini", "stations") ; _ArrayDisplay($res) ; display GUICreate("QUAL ESTAÇÃO ?", 350, 50) Local $idCombo = GUICtrlCreateCombo("", 10, 10, 200, 20) GUICtrlSetData($idCombo, _ArrayToString($res, "|", 1, -1, "|", 0, 0)) GUISetState() While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE Exit Case $idCombo For $i = 1 to $res[0][0] If GuiCtrlRead($idCombo) = $res[$i][0] Then Msgbox(0,"", $res[$i][1]) Next EndSwitch Wend

GUICtrlSetOnEvent(_GUIUtils_CtrlID($oForm, "ctrlName"), yourFunction) 1) you are right 2) I used it to debug the onChange function (window subclass), just comment it (it is not needed for the UDF)

Both posts above already explain this, I've attached the example I used.FILStations.au3FILStations.txt

@ngocthang26 From what I can tell, the socks username and password is only valid if you're using a SOCKS proxy. Since your current code isn't working, you might try something like this instead -- $sDesiredCapabilities = '{"capabilities":{"alwaysMatch":{"unhandledPromptBehavior":"ignore","proxy":{"proxyType":"manual","httpProxy":"username:password@123.31.45.40:1808","ftpProxy":"123.31.45.40:1808","sslProxy":"username:password@123.31.45.40:1808","autodetect":"true"},"goog:chromeOptions":{"w3c":true,"excludeSwitches":["enable-automation"],"useAutomationExtension":false,"prefs":{"credentials_enable_service":false},"args":["start-maximized"]}}}}' It should be obvious, but be sure to replace "username" and "password" with the correct values. 😄

Why go through the hassle of dealing with a behemoth like Symantec, or any other AV company for that matter, over scripts that you create? I could understand it if it were a full-blown application, but these are scripts. If it were me, and I had control over my environment (as any IT department or professional should), I would designate a folder structure that scripts can be run from, apply the appropriate ACLs to that structure, and exclude that folder structure from AV scanning. That way, you don't have to play whack-a-mole with AV companies and you can rest assured that your scripts wont be quarantined due to any AV-related issues.

Here you have something to study and play with: #include<Array.au3> $str = "18,03,48,23" $aStr = StringSplit($str,",",2) _ArraySort($aStr) for $x = 0 to UBound($aStr)-1 MsgBox(0,"value " & $x ,$aStr[$x]) Next Jos

Currently I'm using the PixelSearch command within a loop, and using WinActivate. My issue is that PixelSearch looks either within - 1. A specified rectangular area based on the pixels of your screen resolution. $rectangular = PixelSearch( 599, 113, 648, 160, 0x78B31B) or 2. The entire desktop. (@DesktopHeight and Width) $full_screen_res = PixelSearch( 0,0, @DesktopHeight, @DesktopWidth, 0x78B31B) BUT I need a way to isolate the PixelSearch to an active Window, and THEN the specified rectangular area within that window, being 1920x1080 in resolution. I don't have a screenshot I can share, but the best information I can provide is that the Window will always be a specific resolution (1920x1080), because I'm going to build it that way. If it simplifies the question, I want PixelSearch to search within a specific Window, not my entire desktop resolution. I'm confident this is do-able, but I'm far too new to coding to understand exactly what to search for when self-educating. I know the PixelSearch command itself cannot specify a Window, so I would need to specify this within the loop. My gut feeling is that this doesn't relate to PixelSearch at all, but instead somehow isolating the script itself to a specific Window?

" the other theory is that they are not windows controls "??🙄🙄🤦🏻‍♂️...if they are not "WINDOWS CONTROLS"..then what do you call them? 🤐 all i can see here is " only words with no sense "...they say "The worst wheel of the cart makes the most noise."😏