AutoHotkey (AHK) is a free, open-source macro-creation and automation software for Windows that allows users to automate repetitive tasks. It is driven by a scripting language that was initially aimed at providing keyboard shortcuts, otherwise known as hotkeys, that over time evolved into a full-fledged scripting language.
We’re getting closer to AHKCon which is going to be on August 6th and 7th. Each day we’ll be starting at 10:00 a.m. EDT and going for four hours each day. If you haven’t already signed up to be notified of updates, you can do so here
To be sure we provide content that is helpful for attendees we’re making a few assumptions
You can understand English
You’ve been using AutoHotkey for 6 months (or have 1 year+ programming experience in other languages)
The Conference will be held in a Zoom Webinar and sessions will be the following two formats:
Lectures (people present a “how to” do something with AutoHotkey
Panels (a group of AHK experts discuss a given topic)
While we have a good handle on the topics for the panels, we’d really like to get you to vote on the topics for AHKCon lectures.
We’re working on an advanced course deep-diving into Objects in AutoHotkey. In the Intermediate AutoHotkey course I covered some of the basics of storing data in Objects however, with the help of RaptorX / Isaias Baez I’m creating a course that dives deep into AutoHotkey Objects and Classes
We’re finalizing the outline and beginning to produce the videos. Below is a current peak into what will be covered. If you’d like to stay informed, please complete this short form and we’ll keep you in the loop!
AutoHotkey Objects and Classes
What AutoHotkey objects and classes are and why you should learn them
What can be done with objects
Diving into: Items, Keys, Properties and Methods
Quick refresher on Functions
Object Types (Arrays, Associative Arrays, Multi-dimensional arrays, Maps (new in V2)
Advantages & Disadvantages of Dot Notation and Object Oriented Principles
In programming writing clear code is critical to success! You need to be VERY clear on what you’re asking the programming language to do or you’ll end up with weird, often unwanted, effects.
The “tighter” your code (and language) is, the more likely your goals will match what you waned (this is one of the big criticisms of AutoHotkey V1 compared to V2 which is “stricter”.
For some examples of how you might read things incorrectly I’ve written a few examples regarding our U.S. president Joe Biden. For each statement there is more than one way you can interpret the statement. (adapted from a great read Sleeping Dogs Don’t Lay: Practical Advice For The Grammatically Challenged
You’ll be lucky to get Joe Biden to work for you!
I cannot recommend Joe Biden too highly.
I recommend Joe Biden with no qualifications whatsoever!
Joe Biden has made immeasurable contributions to our country!
NOBODY is better than Joe Biden!
I found myself frequently raving about Joe Biden’s work!
We were teetering on the threshold of bankruptcy last year, and Joe Biden’s efforts pulled us through.
For the services Joe Biden has rendered to our country over the years, we find ourselves deeply indebted!
Whatever task he undertakes, Joe Biden will be fired with enthusiasm!
I would place Joe Biden in a class by himself
So remember to be clear in what you write as to not leave any ambiguity!
Writing clear code / be clear
So regardless of what you’re doing (writing AutoHotkey code, letters of recommendations, instructions, etc. be very careful in what you write!
I try and keep my sentences short and to point. It helps readers follow what you’re saying and helps you write very precisely what you want!
Also be sure to have someone in your target audience read you back what you wrote. It’s amazing how often this will spot glaring errors in miscommunication!
When writing code, breaking things into functions (or their own files) is a great way to make sure you keep things clear and things work as expected.