Debugging and the execution path
Mark Wieder
mwieder at ahsoftware.net
Tue Dec 20 13:54:15 EST 2005
Geoff-
Tuesday, December 20, 2005, 7:51:09 AM, you wrote:
> I have enough windows open when an app is running, I don't want a
> plethora of new ones just because I'm debugging.
> I want a purpose-built debugging window that shows variables, the
> calling chain, and the currently executing code in a single window
> that will go away when execution ends. Of course, within that window
> I want to be able to click on any handler in the calling chain to be
> able to show that handler with where I currently am in it, but I
> don't want or need to be able to see two handlers at once when
> debugging unless I specifically ask for it.
Well, you're certainly not going to get an argument from me. It's not
a case of keep-things-as-they-are or go back to a editing just a
single script at a time. I think a tabbed script editor window with
tabs for each script you're editing or debugging would suit my needs.
The windows-all-over-the-screen thing gets to be a pain.
And of course in *my* debugging window I also want to have the option
of getting down and dirty and seeing the assembly code that's being
executed.
--
-Mark Wieder
mwieder at ahsoftware.net
More information about the use-livecode
mailing list