Not stopping at breakpoints in main class constructor about vscode-as3mxml HOT 5 CLOSED

Are you adding the breakpoint in the constructor of the main class? Last time I tried that, it didn't work for some reason. I suspect that the debugger hasn't fully connected yet. Try adding a breakpoint in an event listener somewhere, and you should see a difference.

Also, when using Chrome, make sure to exit the browser entirely and let VSCode launch it. The debugger won't work unless special command line options are passed in, so if it's already running, it won't work.

from vscode-as3mxml.

humm, I set an on click event and the breakpoint worked but I cant get it to stop on page load.
I tried with: window.addEventListener("load", onLoad, true)
The onLoad function is called but again the breakpoint fails. Do you have an idea how one could set a breakpoint in the constructor to break on page load?

from vscode-as3mxml.

I'm not sure. Like I said, it seems like VSCode's debugger might not be fully connected until after page load or something.

If you open Chrome's developer tools directly, and use its built-in debugger, a breakpoint in the constructor will work correctly, so it seems to be a VSCode issue.

from vscode-as3mxml.

thanks Josh, I got it working by setting an interval, like so:
interval = setInterval(onLoad,1000);

for debugging this is enough.

from vscode-as3mxml.

I found that if you add a debugger statement to your HTML page before you instantiate the main class constructor, the VSCode debugger will pause there as if there were a breakpoint. If you continue the debugging session, your breakpoints will work.

I added a more detailed description about this to the documentation:

https://github.com/BowlerHatLLC/vscode-nextgenas/wiki/Common-issues#debugger-will-not-stop-at-breakpoints-on-startup

from vscode-as3mxml.