Open RedHead90 opened 5 years ago
I had same issue trying to debug my old openfl game. Despite
<haxeflag name="-D" value="fdb"/>
in project.xml had no effect, the -debug
flag changes the thing.
In my case auto connect to debugger works with following launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Flash",
"type": "fdb",
"request": "launch",
"preLaunchTask": "lime: build flash -debug",
"program": "${workspaceFolder}/export/flash/bin/my.swf"
}
]
}```
I had same issue trying to debug my old openfl game. Despite
<haxeflag name="-D" value="fdb"/>
in project.xml had no effect, the -debug
flag changes the thing.
In my case auto connect to debugger works with following launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Flash",
"type": "fdb",
"request": "launch",
"preLaunchTask": "lime: build flash -debug",
"program": "${workspaceFolder}/export/flash/bin/my.swf"
}
]
}
I did everything according to the instructions and now, when I start debugging, my swf file is executed, but the debugger continues to wait until I click the "Debugger" option in the player context menu. Win 10 VS Code 1.33.1 Haxe 4.0.0-rc.2 vshaxe 2.9.2 flash-debugger 1.2.2