#Warn giving incorrect warnings in AutoHotkey 1.1.33.00
Posted: 30 Jun 2020, 18:45
DISCLAIMER: I'm a complete non-coder who is quite new to AutoHotkey and who has only used it for key remapping. I'm running Windows 10 Home 1909, fully up to date with the exception of the most recent Patch Tuesday (for which some users have reported a forced-reboot bug).
I have a laptop with no dedicated media keys, half-height arrow keys, and other navigation keys in a non-standard layout. I run four AutoHotkey scripts, mostly to remap and repurpose the un-numlocked numeric keypad in order to remedy those shortcomings.
My scripts were running fine until I updated from AHK 1.1.32.00 to 1.1.33.00.
After the update, the #Warn setting in my each of my scripts threw warnings for lines of code that are not present in any of my scripts -- specifically that code following a non-existent second or third return (typically equally non-existent Exits) -- would not be executed -- and the scripts wouldn't run.
I commented out the #Warn setting in each of my scripts (; #Warn) and now they run fine again.
Barring beginner's ignorance on my part, something seems to be wrong with how #Warn is working in 1.1.33.00.
I have a laptop with no dedicated media keys, half-height arrow keys, and other navigation keys in a non-standard layout. I run four AutoHotkey scripts, mostly to remap and repurpose the un-numlocked numeric keypad in order to remedy those shortcomings.
My scripts were running fine until I updated from AHK 1.1.32.00 to 1.1.33.00.
After the update, the #Warn setting in my each of my scripts threw warnings for lines of code that are not present in any of my scripts -- specifically that code following a non-existent second or third return (typically equally non-existent Exits) -- would not be executed -- and the scripts wouldn't run.
I commented out the #Warn setting in each of my scripts (; #Warn) and now they run fine again.
Barring beginner's ignorance on my part, something seems to be wrong with how #Warn is working in 1.1.33.00.