Many AutoHotkey V1.1 Commands Offer Parallel Functions Which Run in Both V1.1 and V2.0—It Makes Sense to Use Them Now
I recently noticed an evolution in the online AutoHotkey documentation. Over the past number of years, the powers-that-be have added new functions which serve the same purpose as the traditional command. Yet, they have made no particular effort to highlight the significance of those functions. That has changed. Continue reading →
With Many If Comparison Commands on the Chopping Block in V2.0, Here’s a Trick for Both AutoHotkey V1.1 and V2.0
While driving with her girls buckled in the back seat of the car, my daughter informed her attentive three-year-old and five-year-old of some important details about the day’s activities. After finishing up her explanation, she asked, “Now, does that make sense?” Both girls responded in unison, “Yes, Mommy!” That seemed to settle things until she overheard the three-year-old while leaning over toward the five-year-old whisper, “That doesn’t make any sense!”
AutoHotkey Version 2.0 Drops the GUI gLabel in Favor of the Object OnEvent() Function
In AutoHotkey V1.1, the primary method for adding action to GUI pop-up windows employs the gLabel inserted into a GUI control’s options. As AutoHotkey moves to object-oriented programming in V2.0, the Gui.OnEvent() function replaces gLabels.
In AutoHotkey V2.0, each GUI control responds to different Gui Events. For example, with the Gui Button control, you can register OnEvent() functions for Click, DoubleClick, Focus, and LoseFocus, while the Edit control directly supports Change. You register each type of initiating action you use with the OnEvent() function. In fact, you must register an event before AutoHotkey will respond. Continue reading →
If You Seek a Wealth of Information about AutoHotkey and How It Works, You Can’t Go Wrong with Jack’s AutoHotkey E-Book Library. See the Benefits! Plus, Coming Soon!—More on the Future AutoHotkey Version 2.0 Release
I currently maintain a number of irons in the fire—all AutoHotkey. With three books in the works (two new and one major rewrite), plus regular blogging about AutoHotkey on this site, I find no shortage of things to do. Right now, you’ll find nine AutoHotkey books available at the ComputorEdge E-Books site on topics ranging from an introductory level Beginner’s Guide to a little more complex AutoHotkey Windows scripting, such as, AutoHotkey Applications and Using Regular Expressions in AutoHotkey. By years end, that number should reach eleven books—hopefully. While continuing with the new books, I’ve shifted part of my focus to updating the older books by adding examples of the new AutoHotkey Version 2.0. I plan to increase the versatility of the library regardless of whether readers ultimately decide to upgrade to V2.0 or stick with the current reliable V1.1. If you own one of the AutoHotkey Library Bundles, then you can get these new rewrites with V2.0 examples absolutely free. Continue reading →
When and If the Time Comes, Regular Expressions (RegEx) Can Help with the Conversion Process from AutoHotkey V1.1 to V2.0
Identified by the (v1,v2) on the right side of the script name in the index, I’ve converted a few of the script on the Free AutoHotkey Script page from AutoHotkey V1.1 to the alpha version of V2.0. At first, I reworked a copy of a script one line at a time. Then I speeded up the process with a couple of Regular Expressions (RegEx) used in conjunction with Ryan’s RegEx Tester. While I continued working one line at a time, I could quickly reformat the entire line at once—mostly. Rather than tediously rewriting a command character by character, the RegEx provides a format which needs very little additional editing.
In AutoHotkey V2.0, GUI Pop-up Windows Turn into Objects, Plus Replacing the Lost V1.1 gLabel
I’ve converted a few of the simpler AutoHotkey scripts on the ComputorEdge Free AutoHotkey Script page (AddDate.ahk, EggTimer.ahk, and LaunchWindow.ahk) from V1.1 to the latest alpha version of V2.0. As I convert and post the new .ahk2 scripts, you can identify them by the (v1,v2) found to the right of the script name in the Download Index.