Leaderboard

Hi, Some good news today: Danp2, RTFC and junkew have accepted the invitation to become MVPs. I am sure you will all join me in congratulating them on their new status. M23

https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MacrosforVisualStudio

So, I made this console app--using TreeWalkers of course to walk the UI Tree-- that starts at the root and looks for enabled, active controls--and in piping that to a file, I got this (edited, lots of controls in that list), above. LOL, so, those commands that are stored in memory are control elements! Sweet. this UIAutomation stuff is awesome. @junkew got me into this, blame his IUIAutomation kit. So there is this OLD vb OCX that is super ornery, but his kit can manipulate it, even if it is just SendKeys, So I must build a C# wrapper of my own... LOL this stuff is so cool. I have tried TestStack.White and MANY other wrappers, they seriously suck, no support either. I used canned Microsoft example code too for the most part. This is an extreme for me though, our modern stuff I can test easily enough, but I want my own kit to use to discover and poke around with. I like to use the IUIAutomation tool as a sanity check too, it's very useful.

Local $hPid = Run(@AutoItExe & ' /AutoIt3ExecuteLine "Send(""{UP 999999}"")"') ; simulates the Send("{UP down}") Sleep(10000) ProcessClose($hPid) ; same effect of Send("{UP up}")

Try something like: #include <Array.au3> #include <File.au3> Local $sFolder = "D:\New folder" Local $aFileList = _FileListToArray($sFolder,"*",1) For $i = 1 To $aFileList[0] ConsoleWrite("FileMove(" & $sFolder & "\" & $aFileList[$i] & ", " & $sFolder & "\" & StringReplace($aFileList[$i], "Rev", "") & ")" & @CRLF) ;~ Uncomment line below to Rename Files ;~ FileMove($sFolder & "\" & $aFileList[$i], $sFolder & "\" & StringReplace($aFileList[$i], "Rev", "")) Next

Do stories of encountering software written in autoit in the wild count? Some small company once hired me to maintain a VPS with data mining bots on windows because the previous guy was constantly having to maintain the VPS because the programs he created were unstable and crashing the VPS. I discovered the programs were autoit scripts. Being a fan of the language I was quite amused at how much data these three programs were processing, a chain of API requests and SQL queries. One program was constantly making requests to several APIs and got several tens of keys, then passed it to the next program who would make a call for each of those keys, then the next program would create several queries for each of those keys. It was really testing its limits. There was an API call that dealt with having to MD5 hash a key and the guy used a javascript processing program (not even nodejs, ie or whatever else) to run some MD5 hashing code, it would launch that program once a second.. I was surprised the guy wasn't able to recognize an MD5 hashing function in javascript when he saw one yet wrote all these programs.. I told my employer this was the wrong language for the job so I replaced everything with my own stuff but I did keep a version of the autoit bots maintained just because I wanted to see them functioning and doing that job cause I thought it was kinda cute somehow, probably because how elaborate it was using all these components to deal with things he didn't know how to properly deal with. Replaced the JS md5 hashing function and that JS interpreter with a simple "_Crypt_HashData" call, created a logging system to catch where the crash happened and realized after 3 days of running it built a ridiculous SQL query that killed the server and it could run for weeks with no issues after that, but still it was quite laggy compared to its successor so I had to let it die... Autoits limit is it's single threaded and developing functionality to circumvent this can be more costly than doing everything in another language that is well suited for the task.