Leaderboard

Think you're a bad enough dude to get scripting in "Hard Mode" with a slightly buggy syntax highlighting feature, no function auto completion, no nifty F1 hotkey that takes you to a functions refrence and no error message double clicking that takes you to the error location? If you fancy the above, then congratulations! this is the portable AutoIt setup for you... If you don't like what you hear, then or option would be a better one for you. But if you feel the need to test your skill, ability and ingenuity and all while throwing the minor syntax highlighting bugs to the wind, then read on ahead! Features Include CompileBuildRun/goTidy ProgramAu3CheckAu3InfoKodaCodeWizardCustomized AutoIt3Wrapper*No function Auto CompletionRandom buggy syntax highlighting The HiEditor application was created in ASM and is about 103kb in size and is designed for programming in assembly code. I've created the syntax highlighting section for the AutoIt scripting language that will only highlight native functions for now. One problem persists though, I cannot figure out a way to disable the "" character from acting as an escape character in strings which effects only the syntax highlighting as I mentioned above. Here is an example of this bug caught in action. This editor does not have a console box area like SciTE, rendering you with no built in debugging features, so this is the part where I talk about the custom AutoIt3Wrapper. I've made a few modifications to the AutoIt3Wrapper script that will make life a little easier in portable mode (for this setup), every time you run a script, a pseudo console box will appear with a 1337 skiddy haxxor look showing you everything you would have seen in SciTE, but unlike in SciTE, you cannot interact with it. there is no jumping to errors on double clicks, there is no console functionality (I.E., running commands) and no pretty colors. The AutoIt3Wrapper I've modified is suited for this setup and should allow the setup to run from any directory location free from any registry keys. No files should be created, modified or stored anywhere outside the setup. Might not work on 64bit operating systems, I have not tested it on one yet so I wouldn't know... Download.html - 93 Previous Downloads

Now is the time to READ the help file, not just look at the pretty pictures. You've got the code listed right there. You even have an X as a placeholder for it.

If the button is always the same colour and the text is always the same, I wouldn't just search for a pixel that matches that colour. I'd search for a region that matches a pixel checksum. It's the closest we have to an OCR at the moment. Pick a rectangle roughly the size of the word "OK". I just made some arbitrary numbers and tossed something together without testing it. This is the same method I used in another program for a similar problem. ; First, get the Checksum of the region. $var = PixelChecksum($x1, $y1, $x1 + 50, $y1 + 25, 1, $hwnd) MsgBox(0, "Region", "The Checksum is: " & $var & @CRLF & "Write this down.") ; Now ... in your main program $var = {whatever checksum you arrived at} If _FindButton($var) Then MouseClick() ; and this goes in a function: Func _FindButton($CheckSum) Local $y1, $x1, $result, $hwnd For $y1 = 1 To @DesktopHeight For $x1 = 1 To @DesktopWidth $result = PixelChecksum($x1, $y1, $x1 + 50, $y1 + 25, 1, $hwnd) If $result = $CheckSum Then Return 1 EndIf Next Next Return 0 EndFunc ;==>_FindButton

MouseClick()

This may do it. Add half the width and half the height of the button to the coords (both width and height in pixels), so.. MouseMove($pixel [0] + half the width, $pixel [1] + half the height, 1)

Phil77, First find the colour of the button using the Window Info tool (C:\Program Files\AutoIt3\Au3Info.exe if you did a standard install) - you find the colour under the "Mouse" tab. Then use PixelSearch to find the first pixel of that colour. Finally use MouseClick to click those coordinates - although I would add a few pixels to each one to make sure I hit the button fully. As you might have several buttons, you will need a loop to repeat the process until the PixelSearch function fails to find a button. If there is something else of the same colour on the screen you will need to adjust the coordinates you search to prevent false results. Pretty easy stuff - give it a go yourself and see how you get on. You know where we are if you run into problems. M23

When you click the button using the DOM, control does not return to your script until the dialog has been processed. Usint the mouse-click avoids this since control returns to you immediately after the click is processed. Dale

Hi there. You are an idiot. This is a 5 YEAR OLD THREAD. You should be banned for not being able to read the dates. Control panel and many other things can be disable, but because you're some script kiddy using the age old it's for school excuse, I'm not going to tell you how. And yes I get a kick out of abusing the young'uns. My ass this is homework.