Known issues
- If your AHK v2 interpreter is not recognized and you try to debug an AHK v2 script, an "AutoHotkey execute bin not found: ..." output log will appear and take focus in the AHK++ (v1) output channel (open issue #570)
- The "Select AHK v2 interpreter" command does not work, instead please try to run (not debug) an AHK v2 script and use the quick pick from the "... does not exist" error message (open issue #571)
Fixes
- Add troubleshooting guide
- Fix go to definition in AHK v1 files (#559)
- Remove unnecessary error message "Couldn't resolve AHK v2 interpreter" (#493)
- This has been moved to a output log visible in the AHK++ (v2) output channel
- A "... does not exist" error message will still appear when trying to run an AHK v2 script with an unrecognized interpreter path
- Fix quick pick for "... does not exist" error message on run AHK v2 script (PR #569)
Note: this fix copies your config into your workspace settings. If you don't like this, please manually enter the path via the settings, and don't use the quick pick. Learn more at PR #569.