3/17/2023 0 Comments First class trouble update 1.04![]() ![]() a:: not suppressing the key if ~a & b:: is also present, unless a:: is the first hotkey.a up:: firing on press rather than release if it is the first hotkey and ~a & b:: is present.Fixed ~a & b:: (when disabled with #If) causing a:: to fire on key-up even after activating some other combo.Fixed Alt::, Ctrl:: and Shift:: behaving like normal keys, instead of firing on release as documented.Fixed command line args for embedded script #1. ![]() 1.1.34.03 - June 5, 2022įixed double backspacing of supplementary Unicode characters in hotstrings.įixed a:: not firing if a up:: and a & b:: are present.įixed MinSize/MaxSize being applied incorrectly before the first call to Gui Show.įixed the hook thread getting stuck in an infinite loop if an InputHook has been restarted too soon after being stopped.įixed crashes or undefined behaviour when a blank parameter is passed to FileCopy, FileMove, FileCopyDir, FileMoveDir or FileRemoveDir.įixed dead keys erroneously being reapplied by the keyboard hook after the final character of a hotstring is suppressed (e.g. 1.1.34.04 - August 23, 2022įixed callback functions not being included in the debugger's call stack.įixed MsgBox timeout reported as "OK" if shown within 100ms of startup.įixed Edit control to ignore +WantTab while +ReadOnly is in effect.įixed property_get returning a local var when -d should prevent it.įixed RegRead to support REG_MULTI_SZ values containing empty items.įixed x:=z invoking undefined behaviour. AutoHotkey_L) are listed below.įor older changes, see Archived Changes. Changes & New Features | AutoHotkey Changes & New FeaturesĬhanges and new features introduced by the current branch of AutoHotkey development (a.k.a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |