debugger problem

Timothy Miller gandalf at doctorTimothyMiller.com
Wed Dec 14 16:44:52 EST 2005


Sorry to be tedious. I keep mentioning this on the list. It may nor 
may not apply to you.

This is exactly what happens when you try to debug a background 
script. I've reported it to Bugzilla. It is easily replicated.

I haven't seen it happen in any other kind of script... Except... If 
you're debugging a script that steps into a handler in the bg script, 
then the debug buttons disappear and the script runs to completion, 
leaving the user in a state of perplexity. I've seen this only in 
Macintosh. I don't know if it happens in XP, too.

I'm curious. Might this apply to you?

If so, there are at least two workarounds. One is that the debugger 
works okay on bg scripts if, and only if, you are on the first page 
of the background.

Second, in many cases, though not all, background scripts can be 
moved to the stack script without modification. I think HyperCard 
retreads -- like me -- are more accustomed to putting scripts in 
backgrounds.

Also, I have heard that alternate debuggers or script editors are 
available. I don't how what they're called, where to find them, or 
how well they work. I understand the alternate debuggers do not have 
this flaw.

Hope this helps. Let us know.

Tim

>Hi!,
>
>
>
>I have many different assumptions about what is causing the problem, but
>rather than to keep grasping at straws I have been looking at the Embassy
>and i saw your reply to a debugger question. So here I am
>
>
>
>I'm running Rev 2.6.1 in a windows XP Pro environment.
>
>
>
>I've used Rev since version 2.2.1 and this is the first time this problem
>has come up.
>
>
>
>When I open debugger, or the app I'm testing hits a breakpoint and opens up,
>the debugger has lost the Step In, Step Over, etc buttons at the bottom of
>the window and all of the menu items that are the same (step in, step over,
>etc.) are "grayed out".
>
>
>
>I have deleted and installed different versions of Rev. and it still happens
>
>
>
>
>So I am stumped. And of course the debugger is too good a tool for me to
>have to go back to the old way of testing and fixing.
>
>
>
>TIA
>
>
>
>Cal
>
>
>
>.
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your 
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the Use-livecode mailing list