NET assemblies, plus it will offer new features such as Arrays / Objects and Unicode.
You’ll be able to compile scripts into regular. This fork is a complete rewrite of AutoHotkey classic in C# (by polyethene and other contributors), which will enable cross-platform AutoHotkey. On the other side, some old scripts from the forum might have minor issues. You may not know a lot about it, but Unicode often makes dealing with advanced topics (Windows API), but also hotkeys with special characters (ä, ö, ü, ß, Ø, Њ, ڵ, …) easier. This describes a different script encoding ( learn more…). Contrary to AutoHotkey classic, it is still actively maintained.īugs are usually fixed quickly (given you report them), however, sometimes a change introduces a new bug.ĪutoHotkey_L has hundreds of new features, such as Arrays / Objects + classes (we’ll deal with them later), native COM (another topic we’ll discuss), but also features useful for hotkey scripters, and last but not least 64bit support.ĪutoHotkey_L is offered in an ANSI and an Unicode version. This fork is based on the original AutoHotkey code, and it is developed by Lexikos (Steve Gray). But trust me, they will become useful.Īlso note that AHK classic on 64bit will not work as soon as you reach some advanced topics. You might think “I don’t need Unicode, Arrays, etc., I don’t even know what it is!”. If you choose this version, any bugs you detect won’t be fixed, and you can’t use a lot of new features, such as Unicode, Arrays, COM, …. Unfortunately, Chris has stopped development some time ago. This is the original AutoHotkey version, coded by Chris Mallett. AutoHotkey “basic”, “classic” or “Vanilla” Of course, it depends on your skills and what you want to do, but here are some pros and cons. The first step to do it choosing the right one. Currently, there are plenty of AutoHotkey forks and versions.
0 kommentar(er)
