Use dropdown menu to select required executable in extension settings

[fade2gray]

Please see ...

https://github.com/fade2gray/vscode-autohotkey-1/pull/1

[cweijan]

I understand what you mean, but why do you need to modify the executable file frequently?

[fade2gray]

Hi, I use some old ansi based scripts that I'm trying to convert and need to swap out the executables to see the effect of any changes I've made. I'm not a competent coder and I'm new to vscode and have never used a debugger before.

[Hicsy]

Also, I assume when converting to v2 we will be changing exe frequently?

[fade2gray]

Also, I assume when converting to v2 we will be changing exe frequently?

When I say "ansi based scripts", I mean scripts that will only run using AutoHotkeyA32.exe for which I believe v2 will be dropping support.

[cweijan]

This situation is rare, I will not add new features, you can use the debugger configuration file. template:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "ahk",
            "request": "launch",
            "name": "AHKV2",
            "program": "${file}",
            "runtime": "C:\\Program Files\\Autohotkey\\AutoHotkeyU64.exe",
            "stopOnEntry": true
        },
        {
            "type": "ahk",
            "request": "launch",
            "name": "AHKV1",
            "program": "${file}",
            "runtime": "C:\\Program Files\\Autohotkey\\AutoHotkeyU32.exe",
            "stopOnEntry": true
        }
    ]
}

[fade2gray]

This solution prevents the use of the run command in the context menu. It also requires breakpoints to be stepped through if any have been set.

Also, see #56.