Closed zero-plusplus closed 6 months ago
What major specification change broke the extension? There are multiple debugger engine bugs in v2.0.14. I specifically chose not to make any changes which should have prevented the extension from working, because I use the extension.
Each property of the object is not obtained as described here.
I had mistakenly assumed that this was occurring due to destructive change.
Due to a major change in the debugger specification in AutoHotkey v2.0.14, this extension no longer features correctly.This problem will be resolved in vscode-autohotkey-debug v2.0.0, but it will take some time before release as the source code is being rewritten from scratch.I have changed my policy to provide hotfixes to support AutoHotkey v2.0.14+ in v1.11.x for a while.
Note that it is speed-oriented and will be released with minimal testing, so it may contain bugs.