Hi Mark, As mentioned previously, I was experiencing this in a plugin stack. However I just ran the stack as a normal stack and experienced the same problem. It's definitely related to the use of a front script since if I send the same message to my stack from the message box, debug works fine.
So I guess I have to ask the question again - is this behavior by design when using front scripts, is it a bug, or is it a result of something I am doing (or not doing) in my scripts? Pete lcSQL Software <http://www.lcsql.com> On Tue, Oct 9, 2012 at 5:59 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Pete- > > Tuesday, October 9, 2012, 12:21:57 PM, you wrote: > > > Debug is enabled and I can use it just fine in handlers that aren't > reached > > via a front script. IS there something about front script execution that > > prevents debug from working? > > Depends. If the frontscript is a script from a plugin then it's a > system stack and the debugger will normally ignore breakpoints and > errors in it. > > -- > -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 > _______________________________________________ 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
