Online Help pages

For those of you who have been linking to my online help pages; Thank you very much.
Several months ago Valik asked for the code I used to create those pages.  I sent him a version that was slightly modified to bring it more in line with what he wanted to do.  The idea was to update the look of the official online docs page.
I have no idea if that project is still in the works or not; nor does it matter any longer.
With a new release version of AutoIt due out anytime now I felt it was an appropriate time to discontinue my online help instead of updating it again.  Today being one of the few days when I have the time available to work at a few things I decided to do it now as opposed to doing it somedays after the new release.  Anyone going to that site will now be redirected to the official docs page.  I'll be leaving that redirect in place for a few months so people have the opportunity to change their links.
Again, thanks to everyone for thier support over the last few years that the site has been active.

Tip about @ScriptDir

You may someday find yourself in the situation I was in not too long ago.  It's a script where I was working with several directories and having to use FileChangeDir() quite a bit.  Of course that changes the working directory from it's normal location which is @ScriptDir.  That also meant that in order to use a couple of exe files that were stored in the scripts folder I would either have to use a FileCopy or FileMove to put those files in a folder that is in the path environment; for example the Windows folder.  If I didn't do that it meant that everytime I wanted to call one of those files I had to specify it with @ScriptDir & "\somefile.exe".  Since those files had to be called quite often I chose another route.
Near the top of your script just add the following line.
EnvSet("path", EnvGet("path") & ";" & @ScriptDir)  That adds the script directory to the path environment but only so long as the script is running.  It's not a permanent change unless you use EnvSave("path").  That means I can then call the file without a path and without worrying about what my current working dir is.
Example:
ShellExecute("myfile.exe") would be the same as using ShellExecute(@ScriptDir & "\myfile.exe") but with a lot less typing involved.

My Forum activity

You may have noticed that I have not been quite as active in the forums recently and that all boils down to the following.
Life has simply gotten way to busy again and yes I did that to myself.  I'm officially retired but since that happened I've opened what was to be a small company that would keep me busy for a few hours a week.  The idea being that I could take off whatever time I felt like taking off.  Telling customers "Sorry; I wont be doing any work for the next week or month."  It just didn't work out that way.  The small company now has 3 divisions and the only part of retirement that I have is no employees to manage.
Therefore I have found it necessary to curtail my forum activity a bit.  I usually just do a fast drive-by and perhaps answer a post or two.  The only reason I even get the time to do that is because the forums are set as one of my home pages so everytime I have to use the internet for any reason the forum page will open so I do a quick browse of some of them.  I usually just mark the rest off as read.
I will hopefully get back to my previous participation levels but it is going to take a while to get caught up with my current load.

Things are moving along very nicely now.

As you may have noticed the Dev group has really stepped up to the plate since they got restarted back in May.  There are some nice things happening that should be in the next Beta.  I know Jon wanted to have a new release out before this but there were some new developments that were causing issues and they want that all worked out before the next release.  The last time I looked it appeared that the small issues that remained were pretty much solved with just a couple of minor irritations left.
I still maintain that there should not be any new release version until there has been thorough testing done in the Beta stage.  When a release version comes out buggy then many employers will not allow thier employees to use AutoIt in the workplace and it has a negative impact on the reputation of AutoIt so please don't push for a release before the devs feel comfotable with it.

Update for PCRE Toolkit ia available

There is an update now available for the toolkit.
Download v3.0.0.24 here

There are a few new features and several bug fixes.

Sorry but the help file is still not available, hopefully I will have time to get that done soon.

PCRE Toolkit for AutoIt RELEASED

At long last the first release version of the PCRE Toolkit for AutoIt is available for public download.

If you are planning on working with regular expressions then this may be the only tool you need.

Download it now.

The help file is not yet ready but since you are a developer you should be able to figure it out.
Please post any comments you may have or suggestions for improvement.  I'm also looking for comments about whether the help file should be included with the install or a separate download.

I hope you enjoy using it more than I've enjoyed creating it.

Update:  Gone now are most of the control tool tips in favor of displaying the information in the status bar.

Tutorials

There are a few good tutorials with precise examples of working with AutoIt code.  Several are already listed in the menu at http://dundats.mvps.org/autoit/ and I hope to soon add this one to the list.
http://403forbidden.dyndns.org/?page_id=26

SQLite UDF

This is a great little library with only one minor drawback.  The SQLite.au3 file #Includes File.au3 (Which I seldom use at all) all for the sake of a little 6 or 8 line function.  Now what?
Simple, I'm going to copy that _TempFile() function into a new copy of SQLite.au3, give the function a new name, modify the calls to it with the new name, and then rename the SQLite.au3 file to SQLiteEx.au3.  That will solve the issue and the file changes are very simple with a script doing all the work.  I may even go so far as to make a copy of SQLite.dll.au3 and call it SQLiteEx.dll.au3 and make the asociated chnages for that as well.  Yes there is a reason for doing it and I'll go into those details at a later time.