Remote debugging - expected behavior
MikeKerner at roadrunner.com
Fri Sep 29 09:12:48 EDT 2017
Even when I use breakpoint, I'm having issues with remote debugging, which
On Fri, Sep 29, 2017 at 8:18 AM, Trevor DeVore via use-livecode <
use-livecode at lists.runrev.com> wrote:
> On Fri, Sep 29, 2017 at 12:56 AM J. Landman Gay via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> > On 9/28/17 8:54 PM, Monte Goulding via use-livecode wrote:
> > >
> > >> On 29 Sep 2017, at 7:13 am, J. Landman Gay via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> > >>
> > >> Thanks. One more question: should remote debugging work with
> > script-only stacks that are part of the app? I have several breakpoints
> > but none of them trigger in a test build.
> > >
> > > Hmm… the issue here is script only stacks will not retain breakpoints
> > they are stored in custom properties. I guess this is something that
> > some thought in general as the breakpoints should be retained between
> > sessions in the IDE too.
> > Makes sense. I could have used it today, this app has virtually no
> > scripts anywhere in any stacks, but has dozens of script-only stacks
> > used as libraries and behaviors. That's where the breakpoints had to be.
> > With the introduction of the Levure framework, more people will be using
> > this method now too.
> What I do is type the word “breakpoint” in script only stacks.
> Trevor DeVore
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
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."
More information about the Use-livecode