On 7/11/05 8:34 PM, Timothy Miller wrote:
The details of my debugger frustration, previously described:
It works fine on, for example, a simple mouseUp script in a simple
button. However, if the button sends a message to a handler in a stack
script (for instance), which then sends another message to another
handler, nested or not, the debugger won't follow along. "Script debug
mode" is definitely turned on. Step Into, etc., are absent and/or
dimmed out, typically. Sometimes, I can see the script window open,
several windows back, but I can't get to it until the script is done
executing. I've tried setting multiple breakpoints in each handler,
tried setting breakpoints by script. The script rolls right past them.
I think Eric mentioned this after you wrote last time, but the debugger
doesn't track "send to" messages. It tracks everything else, but if you
"send" a handler to another object the debugger won't follow along.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
