It's that time again.

That season is once again upon us and I just want to take the time to wish everyone all the best for the holidays and the upcoming new year.

Also; for those of you anxiously awaiting the arrival of the new release version.
I suspect that Jon intends to make a Christmas gift of it so check the forums over the holidays.

Congratulations Steve.

I just returned home from a forced hiatus and noticed that we have a new Moderator.  Melba 23.  This is great news and I'm sure he will do a good job.  My most heartfelt congrats to both Steve and whoever it was that decided he should be promoted into that position.

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.

Developer with too many privileges.

The forums are getting totally out of hand at times.
If you look at the thread in Developer Chat regarding updateing the StringRegExp GUI you will see that it is now locked.  That comes from someone who has recently become a Developer.  Unfortunatly that also gives said person Moderator priveledges.  It was locked simply because I answered that I wouldn't be doing any changes to it.  That reply was in response to the question in this thread.
http://www.autoitscript.com/forum/topic/134937-improvements-for-stringregexpgui/page__view__findpost__p__942231
It had nothing to do at all with the person who locked it.  Now we have a Developer who gets into a huff and decides that the RegEx GUI will not be part of the next release.  While I personally don't think it should be part of the AutoIt install that does not mean that everyone will feel the same way.  That was a personal statement and was placed in the post as a reason that I wouldn't be working on that code at all.  In my opinion, that old GUI needs too much work to bring it up to what is really needed for an effective tool.  That is one that will test everything properly and be easy for beginners to use.
While it is no major loss since there are a few other scripts/apps that do the job and do it better in my opinion that is no reason for the attitude shown in the last post of the thread.

Several of the recent developments both in the forums and in AutoIt itself already have me considering whether or not I should even continue with updating AutoIt as new versions become available.  Again this is personal.  I know that others think that functionality should continually be expanded but as far as I'm concerned it has already far surpassed it's primary goals.  Do we need all of the extras?  That depends on what you are using AutoIt for.  I don't.  If the Developers want to go down this road then perhaps it's time for them to start working on AutoIt4.  That way they won't be breaking any existing code because it won't be compatable at all anyway.  They will also have the advantage of being able to restart with well written code based on experience instead of constantly having to either modify base code (that's taking a chance) or having to use clumsy workarounds because of the short comings of the current base.  By the Developers own admission, if they had to do it all over again, the base code would not be the mess it is now.  Take all the GUI code as an example.  The primary developer doesn't want to touch it because of the mess it's in.  That being the case, starting from scratch would seem reasonable.  Throw the old code out the Window.
AutoIt3 is in no way compatable with AutoIt2 so why would anyone worry about  AutoIt4 being compatable with AutoIt3?  There is no need for that and new goals can be set at the time development is started so they know what will have to be done.  Take the new COM code as an example.  It broke a lot of UDF's which had to be fixed.  As far as I remember I only have one UDF using COM at all so it's no big deal.  I don't use or support that UDF anymore so I'll just remove it from my site.
Speaking of my AutoIt site(s) stay tuned for major changes.  The way I'm looking at it right now is this.
My AutoIt online help site will be taken down and temporarily replaced with a re-direct to the official online help site so you won't have the navigation abilities any longer.  That will probably happen within the next couple of days.  The main AutoIt site will undergo major changes.  All that will remain is a list of links to the actual script files and any compiled apps including the PCRE Toolkit.

I still don't have enough time for much forum activity (see the previous post on this blog) and I think with the way things are going right now there is a good chance that I won't be bothered even signing in for much longer.  I have too many things on the go to be worrying about other peoples attitudes and whether or not I might be stepping on thier toes.
Remove a Developers moderator priveledges and I might reconsider, remove the developer and I will probably reconsider.  For now that's all I intend to say about the subject.
Feel free to comment; you won't hurt my feelings at all and it won't change my feelings towards you if I have any.  Here, unlike the AutoIt forums we do have freedom of speech and I'm always willing to listen to a reasonable argument.

My absence from the forum

Many of you have noticed that I have not been very active in the forums recently and a couple have speculated that it has something to do with a couple of  other forum members.  That is totally incorrect.  I've been absent for personal reasons and simply don't have the time to spend there these days.

Those members that I'm close to already know the gory details and the others don't need to know.

I will return to my former posting frequency as time and circumstances permit.

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.

Back under development

After a (rather lengthy) hiatus the Dev group appears to be back on track with 3 new Beta versions in the last week. There have been a few bug fixes and some changes to DLL structures. Only one script I tested failed and as it turned out the problem was not with the Beta per se, The beta did however break one of someone elses UDFs that I was using. I think it's probably related to the way DLL Structs are now handled but I will let the person who wrote it figure that one out.
All I can say right now is it's nice to be rolling again even if it means the odd broken script.

If you run into any bugs using the Beta version; be sure to report them since that is the only way they can be fixed.

More ranting

It appears that Admin is getting some of the new forum problems fixed, that was to be expected.  The preview thread feature is nice if it was implemented in another way.  It still causes an annoying distraction when you run the mouse up and down the page and I like many others use the mouse to follow what we are reading (one of the reasons I don't like [autoit] tags) so it causes the images to pop on and off as well as a very slight difference in the style for the affected thread.

The one I object most to is the Share This "feature" (read as "crap").  None of the forums seem to be immune from that issue so that means in theory that even material in the private forums could be shared on very public Social networking sites.  I'm in favor of eliminating all those sites never mind sharing anything on them and yet some idiot can come along and share my posts with the world on a whim, yes even though some of the material was classed as private.  At this point the thought has even crossed my mind to just remove all my posts and pack it in for good.  For now I'm settling for perhaps reading a bit but not posting anything and that's the way it is going to stay as long as Share This remains.  I'm going to be too busy to participate for a while anyway and this just frees up a bit of time so in the end it will work out at my end.

Forum upgrade?

Well it happened again, the forums get performing almost smoothly and we get another upgrade to break them again.  Okay, Admin spotted the problem with code tags and put a temporary fix in place.  That was good because without at least the text code the forums are of little value.  But a quick scan through the forums reveals other problems (not associated with Admins efforts) brought on by the new upgrade.  as far as I can tell at this point all it does is add more crap to the forum pages, some of which is broken, and all of it is crap that I for one, don't need and more importantly don't want.  I see absolutely no value in the social network sites and even less value in the forums having links to share on said social network sites.  That boils down to more clutter on the forums.  There seems to be some king of an image which is supposed to appear at each post as you move the cursor up and down the page.  Who knows what that image should be because it doesn't appear but having something follow my mouse up and down the screen is just too distracting.  I've made a post asking that someone inform me by Instant Message when the problems are rectified.  That brings it down to a very limited few who know how to contact me, and I indicated that I will be back when the forums are fixed or even rolled back.  I certainly hope there is no costs associated with these upgrades because the last couple have been more trouble than they are worth at any price.  For now, I'm gone.  I've had enough of this over the years, and as much as I enjoy being active in the forums, I see no reason to spend time in a site that is just going to annoy me.  Thanks to all who have supported me over the years and I hope to someday meet up with you again, and a special thanks to the AutoIt developers, past and present, for their efforts.

I will continue to blog here periodically and I will continue development of the PCRE Toolkit but there will be no notification on the forums about any updates.  They will be announced here as soon as the download file is changed on my site.
Goodbye all, at least temporarily.

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.

Time to set some projects aside.

As I mentioned in a recent post, I'm considering that it's time to stop writing code.  Now I know I'll never be away from it 100% but I do need a rest away from it for a while.  Whether or not I will stay with writing in AutoIt is also up in the air.  I will continue to update and patch current released software, however I am retiring several projects that were on the drawing board, even a couple that were near release.

If I start any new projects they will be very small  and in all likelihood will not be written in AutoIt3.  I think the future of AutoIt is up in the air and it may have already reached it's maximum stage of development using the current core.  I can't get the feeling out of my mind that we may have seen the last release of AI with version 3.3.6.1.  In my mind, that's a shame but sooner or later any software will reach a dead-end after which all that's left is simple eye-candy and not more functionality.

I have an offer of help to add some functionality to that I've wanted to the PCRE Toolkit and I am going to take that person up on his kind offer.  If I don't get those additions done then I will never be satisfied with that app and several people know what those additions are and have been looking forward to them.  I would hate to disappint them and myself so that is one project that will stay active.

I also don't think I'm going to be dedicating as much time to the forums, although I will still at least be checking for messages on a daily basis.

To all those that I've been "over the river" with for the last few yers, it's been a slice and keep at it as long as you can or until the fun goes out of it.

Next on the horizon

The release of the PCRE Toolkit now puts that project into maintenance mode until it's time for a major update.  That means it's now time to get on to another project  Which at this point I think will be another Toolkit but this time for SQLite.  Before I get started on that I want to finish up a personal SVN / Bug Tracking project I've been working at.  And of course there is always more work to get done on my latest version of Project Express.

Maybe I'll just take a couple of days off and rethink all this.  As a matter of fact I might just take a few days and rethink AutoIt , after all these years using it, maybe it's time to move on.

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.

PCRE Toolkit updated again

See this post
This is mainly a cosmetic update but a couple of minor bugs were also fixed.

Notice to Fennek

You must be joking when you say that you are going to flood members of the AutoIt forums with spam.  That isn't even good for a laugh and I'm really getting sick and tired of idiots like you, with an IQ smaller than their shoe size, starting this kind of crap.

You're a 16 year old punk who seems to forget thet the people who taught you to write AutoIt code certainly didn't teach you everything they know or even anywhere near what they know.  That list is only a very small percentage of the total members of the forum.  Of those on the list there are several who have been writing code and hacking longer than you have been breathing, and do you think for a second , when you start flooding them with spam, that they won't retaliate?  It would take very few lines of code to write a script capable of messing up your site to the point of it being totally un-usable.  Script kiddies like you annoy us at the best of times so don't push your luck with this kind of nonsense.  On top of that I already have good mail protection but if I so desired I could let yours through long enough to not only get your ip but to get the address where we should report it and then that address gets flooded with abuse reports.  Do yourself a favor and pull it now before some fool actually follows up on what you started.  When that happens, it won't matter who actually sent the spam, it will be you that takes the fall for it.

You might not care about the reputaion that AutoIt gets from garbage coders like yourself but we do and we will put a stop to it.

Malicious code

There is a trend that seems to come and go in waves and right now it's at a high point again.  That is people asking for help with code which is meant to be used for either malicious reasons or to bypass some security feature like a Captcha or the biggie, cheating at a multi-player game when the TOS explicitly states it is against the rules.

Just a note for those people.  Stay away from the AutoIt forums, we don't need you nor do we want you there and you must be wise enough to know you shouldn't go where you are not wanted.  That would just make you subject to a lot of abuse.

We are also aware that such abuse will (in your mind) be our fault but we are all willing to live with that as long as you just go away.

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.