Forgot about those tools. I did try a demo of Remo at one point, don;t remember why I didn't buy it. Pete Molly's Revenge <http://www.mollysrevenge.com>
On Wed, Apr 20, 2011 at 1:19 PM, Bob Sneidar <b...@twft.com> wrote: > Both Remo and GLX2 have script editors that turn a called handler into a > link you can click on and go to the command or function. U should give them > a try. Remo is current. GLX2 is legacy and no longer supported. Remo uses a > method of breakpoints that are evaluated at runtime and stored, but it does > not step through the code. GLX2 has a code stepper, but there can be some > problems with that. A few commands will lock up the stepper it seems. Both > were written by Jerry Daniels and friends. > > Bob > > > On Apr 20, 2011, at 12:04 PM, Pete wrote: > > > Yep, I'm doing just about all those things. What I didn't do is use a > > naming convention that indicates where in the message path the called > > handler is. So if I call dbDoit from a control, where does dbDoit > reside? > > In the control script, on the card/stack that the control is in, on the > > mainstack for the app, in some library totally outside the main stack > that's > > been inserted as a front/back script, stuff like that. > > > > Pete > > Molly's Revenge <http://www.mollysrevenge.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 > > _______________________________________________ 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
