I have not. I broke the remote debugger and haven't played with it in a month or more. What I was thinking of doing was having a breakpoint wrapper that only fires if I have a variable or property set, e.g. a global called "debug", or having my "execute" debug method, that gives me an answer box, lets me type in any LC statement I want, and then "do"es it fire a breakpoint
On Tue, Jan 23, 2018 at 4:15 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > On 1/23/18 12:27 PM, Mike Kerner via use-livecode wrote: > >> @JLG I thought with "breaktpoint" you could debug SOS behaviors >> > > I haven't actually tried that yet. It would be more difficult to avoid > debugging when you just want to run the stack normally but would be better > than nothing. I suppose you'd need to remember to remove all the breakpoint > commands from the SOS files at some point. Have you tried it yet? > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ 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
