doBreak – very useful for debugging code from .as files. Since breakpoints for .as files are not saved between executions, you have to manually set them each time you want to break inside a .as file. Instead, add:

function doBreak(msg)
{
trace(“doBreak: ” + msg);
return;
}

to your first frame. (Always on a seperate Actions layer!!) Add a breakpoint at the trace statement. Then call doBreak whereever in your .as files, run in debug mode, and the program will break inside the doBreak. Then press the “step out” button and you’re at the right place for debugging. Props to “Alan Prather” for the tip.

http://chattyfig.figleaf.com/flashcoders-wiki/index.php?Best%20Practice

Same here.

Um… one thing to try:

…fuggit, I’ll test:

Hrm. I put some code on _root, and then compared that with an SWD that had a breakpoint. The SWD’s are different, but they are all that weird programmer shite in Notepad.

Hrm… sorry bro, don’t know.

Yea I knew about that way, but the issue there is I may have over a 100 classes for one project, I’d rather not have to go in and set it everytime. I’d like to save that type of setting or just place it in a file. Placing the debug statement in the file itself is a little sketchy because then altering breakpoints becomes a pain. But implementing it everytime is a pain. It would be nice to have a debug file. Again..I may b missing something.. my eyes are blurred and my brain is confused at this point in the day.

When you first run the debugger, you know that message that says set breakpoints? Well… do it. I always ignored it, but actually, that dropdown/combobox actually contains all of your external code as well.

Before you hit the play button, go into your code, and set a breakpoint. It may be tough to find it if your using a lot of includes/imports, but she’s in there. Then hit play.

That way, if your using external code (better if your in 2004), you can debug your code with breakpoints.

In the case that you find 2 copies of your code, try the first; if you cannot set a breakpoint, then try the second. One will work and one won’t; happens everytime.

Also, if you see another prompt, don’t worry, it remembered your first breakpoint; it’s either just a level or shared library and it’s SWD was just loaded.