erik hansen wrote: > my problem now is that "breakPoint" is not acting > as a debug breakpoint and i can not step through > my handlers.
Unlike HyperCard, the debugger doesn't open when it hits a breakpoint statement. If you leave the debugger open while you run the stack though, the breakpoint does trigger and then you can step through the script. That allows you to run the script normally without removing the statements, but still debug when you want to. But it is easier to just open the debugger, click on a line to set a temporary breakpoint, and forget about putting the statement into your scripts at all. Caveat: The debugger won't let you abort a running debug session unless it hits an error. That's something to remember, if you are testing a script that deletes things. I got bitten by that once. I could see as I stepped through the script that an upcoming line was going to ruin my stack and there was nothing I could do but watch it happen. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
