Celeri

Wow ... amazing! It's missing a "clear" button however. If you do 2 consecutive searches, both results are merged. Which might be wanted sometimes, but not all the time. I'm presently checking if there's anything at any place that can be streamlined to go faster. I'll keep you guys posted (and so far nothing )

Tested and so far it's true - 3.2.6.0 is very much FASTER. I suggest you upgrade and test again P.S.: Thanks for the encouragement Sandman Where do I apply for the toaster?

Ok so it looks I'm going to have to reply to myself to get any input here So anyways, just discovered 3.2.6.0 is out and it boasts a 30%-40% speed increase ... we'll be the judge of that Download the new version here: http://www.autoitscript.com/forum/index.php?showtopic=51967 I'll keep you posted with some observations in the following days. See ya!

Nope. But it all depends what you want to do. In my case, I use hotkeys to set a variable named $Hotkey and $Hotkey is evaluated at different points parts in the program like so: If $Hotkey Then ConsoleWrite("Number "&$Hotkey&" is the winner!") And here's some typical code to setup the hotkeys ... read the comments! Func Set_HOTKEY() For $i = 1 to 8; Keys 1 to 8 on the keyboard HotKeySet($i,"Def_HOTKEY"); Notice all point to the same function - There's a trick! Next EndFunc Func Def_HOTKEY() If @HotKeyPressed > 0 And @HotKeyPressed < 9 Then; @HotKeyPressed can be used to set a variable $Hotkey = @HotKeyPressed; In this case the variable is the hotkey pressed. You could use switch Else; and set up different variables/functions depending on what you want to do and what key is $Hotkey = 0; pressed ... EndIf; The check on the first line is superfluous but you never know;) EndFunc Don't forget to set Global $Hotkey at the top of your program!

As far as reducing pictures go (if that's your bag), you can use Photoshop, load your photo --> Mode --> Indexed Color --> Palette = Local (selective) --> Forced (none) --> NO transparency --> Dither (none) --> and then reduce the colors from 255 to 0 until it hurts Photofilter (which is free) also does something similar although with less finesse. http://photofiltre.free.fr/ After that you can save a gif and use a program like "gifopt1.0" to remove all useless headers. Or the online version (one of them!) http://tools.dynamicdrive.com/imageoptimizer/ If you use GUICtrlCreateGraphic you'll see it accepts Gifs and Png (I suspect this is related to Internet Explorer). In your case BTW, I would also try JPG, and then strip all the headers with a program called stripper (in google type "stripper jpg" without the quotes)

That much is clear However my mom can program AutoIT3, but I doubt she'd get along with C++ or C# ahahahah

Mind you, it depends. If you're working with files and file transfers in AutoIT3, the difference in speed with C# or C++ will be minimal since the program will be dependent upon Harddrive latency. I once made a cleaning program in AutoIT3 and it was up there with CCleaner in terms of speed

I wonder ... I never tried it but do you think copying files to a burner on XP/Vista will automagically have windows prompt the user to burn the files? I'm saying this because I already tackled the CD/DVD burning question a while ago and honestly, there was little solutions at that time. If that doesn't work, there's IMGBurn which has an interesting command line, CDIMAGE which is freeware and a few others that I can't remember for the moment. In any case It's a pretty big project and last time I tried I litteraly broke my neck Thanks and keep up the good work!!!

Since AutoIt is an interpreted language (as compared to a compiled language) the difference will probably pretty big (not in favor of AutoIT3). Hey anyone here can prove me wrong?

Ok, I don't want to pick a fight (ahahahah) Anyways we almost agree So here's my take on this. Take a smal program that checks a filename (hey I'm working on that!) Here's what can go wrong: 1. Does it contain illegal characters? 2. Is it null ""? 3. Is it too long? 4. Does it contain too many wildcards? ("*" and "?") So in fact there are at least 4 different types of error here. There is only one instance where there is no error and that's when all the four previous checks are ok. So it makes more sense if the returned values are: 0. No problemo 1. Invalid characters 2. Null string 3. String too long 4. Too many wildcards. In any case we usually check to see if there is an error rather than the reverse. So ... If _CheckMyFilename("Celeri_?????_with_his_RunDLL_Calls.bak") Then ConsoleWrite("I made a boo-boo")makes perfect sense. However If _CheckMyFilename("Celeri_?????_with_his_RunDLL_Calls.bak") Then ConsoleWrite("Wow you made it!")is not quite as practical. Oh well, to each is own I guess

Not sure. Let me quote the help file for Set Error: SO unless I read wrong, no error, no returned value. If error, than a value that correspond to a specific error. Per example, error 1 would be "One of the windows does not exist". Error 2 could be error returned by RunDll, the extended code could be that error #. BTW I'm a complete dork with DllCalls so you got me there

I'd also combine both verifications: If WinExists($TitleP) And WinExists($TitleC) Then And add Opt("WinTitleMatchMode", 2) into the function Now it's looking good too

Allright just a fast reply ... since I read the code (didn't run it yet). You should declare all variables Local Local $HwndP, $HwndC, $user32 For quickness and standardisation, on error you should return 1, on no error you should return 0 Why? If _SetParent("- SciTE", "Mozilla Firefox") Then MsgBox(0,,"","Big ERROR") You save a few lines of code also. If NOT _SetParent(... will do something if there is no error BTW.

Good timing! I was looking for something like this! I'll test it this week and come back to you. P.S.: A lot of people here just download and go, they don't bother to comment. Don't despair there's still a few good guys (and gals) around to help you out and comment.

Thanks! I started learning C++ but I'm lazy and I have a limited amount of time. AutoIt's learning curve is really, really low Although there's a few quirks here and there but you get used to it. I'll keep on comparing - if any of you has anything interesting, post it and I'll add it to the first post