It’s unlikely that anyone will attempt to force you in one direction or another. If you opt to venture into V2.0, then the change probably won’t cause as much pain as you might imagine. If you desire, you can stick with the old version of AutoHotkey without any impact. When AutoHotkey V2.0 arrives as a full release, only you will decide if it works for you. If you’ve amassed a considerable number of scripts written for V1.1, then the task of converting to V2.0 (which drops numerous traditional commands) looks daunting. The words “sacrificing compatibility” may strike terror into your AutoHotkey plans.
Note: As an important caution, while AutoHotkey V2.0 continually marches forward toward eventual release, it currently resides in alpha testing and you should not yet install it as your primary AutoHotkey program-unless you understand exactly what you’re getting into. In spite of all that, I offer this blog as an aid to current and future AutoHotkey users in their version decisions.Īs stated in the online documentation, “AutoHotkey v2 aims to improve the usability and convenience of the language and command set by sacrificing backward compatibility.” V2.0 simplifies things by removing many traditional AutoHotkey commands and replacing them with clearer, more consistent functions.
Since I written so many AutoHotkey books, you could even say that I hold a vested interest in the current version of AutoHotkey. You might consider my words rank speculation-although drawn from my years of working with AutoHotkey V1.1. I base all my thoughts on information freely available in the online documentation, forums, and other AutoHotkey sources. I’ve had no contact with anyone who has the answers. I start by admitting that I have no special insight into AutoHotkey V2.0. As Signs of the Impending Release of AutoHotkey V2.0 Crop Up in the Online Documentation, Questions Arise About Our Legacy Scripts
0 kommentar(er)
