Peter Haworth <pete@...> writes: > > When I'm stepping through my code in debug and I step into a call to an > engine command or function, the debugger simply goes to the next statement > in my code not to the engine code. > > Does anyone know the mechanism by which the code of engine > commands/functions is ignored by the debugger?
That's by design to keep you out of trouble in endless loops, etc. If that doesn't bother you and you won't lose unsaved work you can do a global gRevDevelopment; put true into gRevDevelopment from the messagebox. And put false back in there when you're done playing around in the system stacks. Note: this will also reveal bugs in the IDE stacks, so ignorance may be bliss. -- Mark Wieder mwie...@ahsoftware.net _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
