Re: message path function

yes, but it makes it harder to work on other things. On Sun, Sep 11, 2016 at 12:02 PM, J. Landman Gay wrote: > Did you try setting the gRevDevelopment global to true? That is supposed > to allow you access to normal debugging in the IDE. > > Jacqueline Landman Gay

Re: message path function

Did you try setting the gRevDevelopment global to true? That is supposed to allow you access to normal debugging in the IDE. Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On September 11, 2016 10:32:22 AM Mike

Re: message path function

When you are debugging the script editor, things like breakpoints don't work. When I hit a "pass", figuring out who the caller was can be a little hairy. On Sun, Sep 11, 2016 at 9:11 AM, wrote: > Hi. > > > Breakpoints don't work? Hard breakpoints? Has v.8 (?) gone that batty?

Re: message path function

Hi. Breakpoints don't work? Hard breakpoints? Has v.8 (?) gone that batty? But what does the "next pass" mean? Or the "next stop"? Are we talking about the message path or subsequent breakpoints in the execution flow of your handlers? Craig Newman -Original Message- From: Mike