| |
xIII
Registered: Nov 2008 Posts: 210 |
Autostart VICE & C64Debugger in VSCode
After I cleaned up my output dir in VSCode, pressing F6 or Shift F6 doesn't automatically starts Vice or C64Debugger after the .prg is build :(
I removed a .vscode folder but after changing the settings again, it was back.
Settings.json looks like this:
{
"kickassembler.debuggerRuntime": "C:\\C64_VisualStudioCode\\C64Debugger\\C64Debugger.exe",
"kickassembler.emulatorRuntime": "C:\\C64_VisualStudioCode\\VICE35\\bin\\x64sc.exe",
"kickassembler.javaAllowFileCreation": true,
"kickassembler.javaRuntime": "C:\\C64_VisualStudioCode\\Java\\bin\\java.exe",
"kickassembler.assembler.jar": "C:\\C64_VisualStudioCode\\KickAssembler\\KickAss.jar",
"kickassembler.outputDirectory": "C:\\C64_VisualStudioCode\\_MyCode\\_OUTPUT"
}
Is the double backslash \\ ok ?
ANyone had the same problem and managed to solve it ? |
|
| |
oziphantom
Registered: Oct 2014 Posts: 478 |
is this VSCode or the KickAss VSCode extension? |
| |
xIII
Registered: Nov 2008 Posts: 210 |
I use the Kickassembler extension by Paul Hocker. |
| |
xIII
Registered: Nov 2008 Posts: 210 |
I removed and re-installed VScode and the extension, also renewed all settings (paths to java/kickass/vice/C64debugger).
I also noticed that the Kick Assembler Memory viewer doesn't display the allocated memory anymore.
It drives me crazy so any help would be appreciated :) |
| |
Lubber
Registered: Jan 2002 Posts: 26 |
For the record: This is fixed in 0.7.7 of the extension |
| |
xIII
Registered: Nov 2008 Posts: 210 |
Yes! Thank you very much for the fast update ! |
| |
Compyx
Registered: Jan 2005 Posts: 631 |
What was the issue? |