Xandy

Probably not before we do The only way I learn is through trail and error. You are doing great. As for where to put the body of the debug function out(), that is difficult for me to specify. You could make a new script called Debug.au3 and copy the function definition there (to the new script). Then you can: #include "Debug.au3"; Quotes "" because it's a custom include file Inside any script you wish to use your custom debug functions. However you can name the Debug.au3 any unique name you wish. You could alternatively copy the function body to any script that would call 'out()'. I don't see the need to tell you how to structure your code at this time. I also do not want to pigeon hole you into my coding practices, as they might not be right for you at this stage of your development. It's your code, Sir.

I see that you believe the script to fail at the configuration section. Perhaps Running the application twice is the problem. We could check to see if the app is running before running the app. We could apply some effort in that direction, if you also think that could be the problem.

Add some debug output. For example: ConsoleWrite('WinWaitActive finished') after the line:   WinWaitActive("WinZip Self-Extractor - SAWStudio64Demo_V1_4.exe") Would look like this: WinWaitActive("WinZip Self-Extractor - SAWStudio64Demo_V1_4.exe") ConsoleWrite("WinZip Self-Extractor - SAWStudio64Demo_V1_4.exe COMPLETED") You very likely will need more of these ConsoleWrite() outputs. Find how far the script reaches when it fails and we'll debug that problem specifically. Here is a function to make ConsoleWrite() output easier to manage: ; Debug function to simplify ConsoleWrite() output lines Func out($out1 = "", $out2 = "", $out3 = "", $out4 = "", $out5 = "", $out6 = "", $out7 = "", $out8 = "", $out9 = "", $out10 = "", $out11 = "", $out12 = "", $out13 = "", $out14 = "", $out15 = "") ConsoleWrite($out1 & " " & $out2 & " " & $out3 & " " & $out4 & " " & $out5 & " " & $out6 & " " & $out7 & " " & $out8 & " " & $out9 & @CRLF) EndFunc ;==>out The function above will allow you to append strings and variables all on a single line then move the output text cursor to the next line after the function call. So you are not constantly adding "& @CRLF" to the end of every ConsoleWrite manually.

My understanding of a nested function would be: Func Fruit() Func Apple() ; Apple Code EndFunc; Apple Func Cavendish() ; Cavendish Code EndFunc; Cavendish EndFunc; Fruit As far as I know, the above would not execute and be improper in AutoIt.

Honestly I don't really know. It's difficult for me to approve your structure logic without the code meat. I worked all day, if there is a slight structure fail. I'm not likely to notice it right now. Best of luck mate. I hope you enjoy your time programming. I always do.

No, I don't think so. Seems legit to me. That can certainly be done. DirCreate(path) DirMove(source, dest, flag); use help file for flags FileMove(source, dest, flag); use help file for flags There could be better ways, but those are some tools above.

Looks like a good start. Sure, what would you like this script to do? What type of 'call' would you like the script to make? Will it be voice telephone calls, or something else?

Your character alone is all the ego you need.

I know what it means.. and it's perfect.

Hey there, will it be okay if I rename variable: pause to Paused? So that changing: Paused by returning value from MsgBox will flag release from loop. Just a second.

I would use SDL. You'll setup an SDL environment. I'll help if you're interested. Then you'll be able to create a screen surface attached to a GUI. Then load image files to SDL_Surfaces and blit (draw) them to the screen surface or other surfaces. Once the images are loaded into a SDL_Surface just redrawn at different positions or even animated by drawing a different surface at position. The UDF by AdmiralAlkex! Click [ MapIt ] in my signature for quick example of complex script using SDL (with pictures) Idk if the scripts currently work, but I do know I can help you with something and get you started. Scroll a little bit and you'll find a short video. Idk man good luck!

Try: _ScreenCapture_Capture or Sorry no guarantees. On my way to work. Good luck

I don't know anything about the AutoIt Recorder. However there are other ways to record. Every time a click or special keypress is captured add the mouse offsets to a list. It might be a good idea to run this code too. To see if there are any hidden windows with the same name as the window to wish to automate. $sTitle = 'Indira Diet' $aWin = WinList($sTitle) ConsoleWrite("Found " & $aWin[0][0] & " Windows named: " & $sTitle & @CRLF) People can help you better if you show the codes you are trying. Best of luck. Happy coding

Bump: Source added to first post.

I thought Unix had a shell scripting language. I used in Tech school about 20 years ago. That seemed like AutoIt for Unix. Edit: I almost completely forget the name of what I am talking about.