Re: Remote debugging - expected behavior

Oh right. I should have thought of that. On September 29, 2017 7:20:29 AM Trevor DeVore via use-livecode wrote: What I do is type the word “breakpoint” in script only stacks. Trevor DeVore ScreenSteps -- Jacqueline Landman Gay |

Re: Remote debugging - expected behavior

Even when I use breakpoint, I'm having issues with remote debugging, which is QR...something. On Fri, Sep 29, 2017 at 8:18 AM, Trevor DeVore via use-livecode < use-livecode@lists.runrev.com> wrote: > On Fri, Sep 29, 2017 at 12:56 AM J. Landman Gay via use-livecode < >

Re: Remote debugging - expected behavior

On Fri, Sep 29, 2017 at 12:56 AM J. Landman Gay via use-livecode < use-livecode@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@lists.runrev.com> wrote: > >> > >> Thanks.

Re: Remote debugging - expected behavior

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 wrote: Thanks. One more question: should remote debugging work with script-only stacks that are part of the app? I have several breakpoints

Re: Remote debugging - expected behavior

> On 29 Sep 2017, at 7:13 am, J. Landman Gay via use-livecode > wrote: > > Thanks. One more question: should remote debugging work with script-only > stacks that are part of the app? I have several breakpoints set but none of > them trigger in a test build.

Re: Remote debugging - expected behavior

This sounds similar to a problem I have building apps. I have a login stack that I call modally when the main stack is opened. When I build the app it OPENS THE LOGIN APP MODALLY as though it is actually RUNNING my scripts, and since it is modal I have to manually set the stack to top-level for

Re: Remote debugging - expected behavior

well, now it's there, so I commented on it, there. On Thu, Sep 28, 2017 at 5:34 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I just opened a new report before I read your post: > http://quality.livecode.com/show_bug.cgi?id=20487 > > I'm not currently testing

Re: Remote debugging - expected behavior

I just opened a new report before I read your post: http://quality.livecode.com/show_bug.cgi?id=20487 I'm not currently testing script errors, I'm testing other things and I don't need remote debugging right now. It's getting in the way. On 9/28/17 3:32 PM, Mike Kerner via use-livecode wrote:

Re: Remote debugging - expected behavior

Thanks. One more question: should remote debugging work with script-only stacks that are part of the app? I have several breakpoints set but none of them trigger in a test build. On 9/28/17 2:16 PM, panagiotis merakos via use-livecode wrote: Hi Jacque, This is the expected behaviour. The

Re: Remote debugging - expected behavior

Then why not remove remote debugger from the (cluttered) inclusions list and only include it if the developer chooses 'test' (similar to what Monte was wondering in that QR). It seems weird and unnecessary, and possibly insecure to do it otherwise (insecure because if you forget to remove it from

Re: Remote debugging - expected behavior

Hi Jacque, This is the expected behaviour. The remote debugger is included in the standalone when you click on the Test button, even if you don't select it in the Inclusions (the same applies to Android Internet permission). See the discussion in this bug report:

Remote debugging - expected behavior

What is the expected behavior of remote debugging? I'm not sure if what I see is how it is supposed to work, or a bug. I have an app that does not have the remote debugger included in the Inclusions pane. Looking at the revStandaloneSettings custom properties, it is (correctly) not in there