AutoHotkey Community

[whynot]

Just discovered this program earlier this week, and so I figured I'd post some of what I've came up with to contribute to the community. If these are redundant, I apoligize, but I didn't find similar code when I searched the forums which researching towards the development of the scripts.

My goal when setting out was to create a series of autocomplete and triggerable events which would act globally, across all applications, in a universal way. This will allow me to easily switch between editors and always have the same key-triggers and styles. Additionally, it lets me now use the same keyboard shortcuts & autcompletes ("", [], {}, etc.), which I would when editing code, when I'm entering code anywhere.

This also makes it easy to keep a similar environmen t between my work PC, and my home PC. By simply keeping AHK's .ini file synced between home & the offive, my development shortcuts and tools that I've written, and use daily, are now all in sync wherever I'm working.

The code I'm going to post below is early in development, and quite realistically my first scripts. But they're working great for me, so hopefully they will for you too. Much of the code is oritented towards web development, and more will be added soon. If there's enough interest, I'll post updates down the road, as these will be quickly growing for me. AHK is exactly the kind of program I've been looking for, so I've got lots of code to write in order to eliminate many of the tasks which I'd previously cobbled together with Automate 5 (A nice program in itself, but not especially suited for a lot of what I want to do).

One more note: When I write script, I tend to outline branches and sections as clearly as possible so that future work and revisions or whatever is easy. Although the web display might be off to due to fonts or CSS or something, it really does help me when viewing it in a text editor (notepad, homesite, ultraedit, whatever). The following should help to explain the code in case it's not clear enough -It works for me at least...

Double lines (equal signs, '====') are used for the very first and last lines of a section.

Single lines (dashed, '-----') seperate a scripts header/information from its code.

Lines of tildes ('~~~~') are used for the beginning and ending lines of a script.

All scripts should have their shortcut key listed in the header section, if they have one.

Where appropriate, I've made it so that the HTML shortcuts don't work when the active Window has the word "Microsoft" in the title. This should help to keep my code editing shortcuts from interfering with those of Office, Outlook, Excel, etc.. In such cases, they'll simply pass the keystroke/trigger through to the app. Other apps can also be filtered in this way. For example, some of the HTML-oriented scripts pass through the event rather than firing when Homesite's the active window, and I'd prefer to use Homesites built in functonality over that of my scripts.

Similarly, it'll also make it so that the scripts won't work with IE. I could write a workaround for that, but I don't use IE, so it's not a concern for me.

Let me know if you find these interesting,, and/or if you'd like the updates as they're added. Also, any comments or critique is appreciated. As I said... My 1st scripts, so I'm open to ways to optimize code.

[Chris]

Looks good. A few minor points: I edited your post to use a "code" section so that its indentation (tabbing) is preserved. This makes it display nicer and also allows someone to copy & paste the script without losing its indentation. Although some of your lines now wrap to a new line due to being too long, they too will be copied and pasted correctly.

I notice at least a couple places where you have a hotkey label conditionally defined. This will not work because labels are processed at the time the script is loaded, not while it is being run. In other words, you can't conditionally define a hotkey at runtime (except by using the Hotkey command):

[Beastmaster]