Re: Remote debugging - expected behavior

2017-09-29 Thread J. Landman Gay via use-livecode 

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 | 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

Re: Remote debugging - expected behavior

2017-09-29 Thread Mike Kerner via use-livecode 
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 <
> 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. 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.
> > >
> > > Hmm… the issue here is script only stacks will not retain breakpoints
> as
> > they are stored in custom properties. I guess this is something that
> needs
> > 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
> ScreenSteps
> ___
> 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

Re: Remote debugging - expected behavior

2017-09-29 Thread Trevor DeVore via use-livecode 
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. 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.
> >
> > Hmm… the issue here is script only stacks will not retain breakpoints as
> they are stored in custom properties. I guess this is something that needs
> 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
ScreenSteps
___
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

Re: Remote debugging - expected behavior

2017-09-28 Thread J. Landman Gay via use-livecode 

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 set but none of them 
trigger in a test build.


Hmm… the issue here is script only stacks will not retain breakpoints as they 
are stored in custom properties. I guess this is something that needs 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.


--
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

Re: Remote debugging - expected behavior

2017-09-28 Thread Monte Goulding via use-livecode 

> 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.

Hmm… the issue here is script only stacks will not retain breakpoints as they 
are stored in custom properties. I guess this is something that needs some 
thought in general as the breakpoints should be retained between sessions in 
the IDE too.

Cheers

Monte
___
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

Re: Remote debugging - expected behavior

2017-09-28 Thread Bob Sneidar via use-livecode 
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 the 
standalone builder to continue. It did not do this in 8.0.x. It started in 8.1. 
I just deal with it like you have been doing. 

Bob S


> On Sep 28, 2017, at 11:45 , J. Landman Gay via use-livecode 
>  wrote:
> 
> 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 either.
> 
> Every time I do a test build, LC asks if I want to start a remote debugging 
> session. Until I noticed the dialog, I thought the app had hung on launch. I 
> have to provide a response on every test build before the app will run. Also, 
> even if I just relaunch the app after installation, it asks again. Basically 
> I can't run the app without replying to the dialog. Is this correct behavior?


___
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

Re: Remote debugging - expected behavior

2017-09-28 Thread Mike Kerner via use-livecode 
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 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:
>
>> 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 the inclusions when you build, your app is open to
>> being remote debugged by someone who is not authorized).  I ask here,
>> rather than adding to that QR or starting a new one, so we can discuss it
>> before I propose it.
>>
>> On Thu, Sep 28, 2017 at 3:16 PM, panagiotis merakos via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>> 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:
>>>
>>> http://quality.livecode.com/show_bug.cgi?id=19370
>>>
>>> If you think this is not expected behaviour, please file a report for us
>>> to
>>> reconsider.
>>>
>>> A workaround to prevent the remote debugger from being included in the
>>> standalone is to turn off the wifi in your Android device (or connect to
>>> a
>>> different network than the one your machine is connected to). I have not
>>> tested it but I suppose it will work.
>>>
>>> Best,
>>> Panos
>>> --
>>>
>>> On Thu, Sep 28, 2017 at 7:45 PM, J. Landman Gay via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>
>>> 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 either.

 Every time I do a test build, LC asks if I want to start a remote
 debugging session. Until I noticed the dialog, I thought the app had
 hung
 on launch. I have to provide a response on every test build before the

>>> app
>>>
 will run. Also, even if I just relaunch the app after installation, it

>>> asks
>>>
 again. Basically I can't run the app without replying to the dialog. Is
 this correct behavior?

 Also, as I mentioned before, if I say "yes" to the dialog, and quit the
 app via the Home or App Switcher, there is no message that debugging has
 been discontinued. I am pretty sure that's due to the fact that LC

>>> doesn't
>>>
 send any messages with those keys. At any rate, when that happens, the
 scripts can't be edited as they are still in a locked state and I can't
 find a way out of that unless I quit and relaunch LC.

 What is the expected behavior? There's no toggle to control remote
 debugging.

 --
 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

 ___
>>> 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
>>>
>>>
>>
>>
>>
>
> --
> 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

Re: Remote debugging - expected behavior

2017-09-28 Thread J. Landman Gay via use-livecode 

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:

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 the inclusions when you build, your app is open to
being remote debugged by someone who is not authorized).  I ask here,
rather than adding to that QR or starting a new one, so we can discuss it
before I propose it.

On Thu, Sep 28, 2017 at 3:16 PM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:


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:

http://quality.livecode.com/show_bug.cgi?id=19370

If you think this is not expected behaviour, please file a report for us to
reconsider.

A workaround to prevent the remote debugger from being included in the
standalone is to turn off the wifi in your Android device (or connect to a
different network than the one your machine is connected to). I have not
tested it but I suppose it will work.

Best,
Panos
--

On Thu, Sep 28, 2017 at 7:45 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


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 either.

Every time I do a test build, LC asks if I want to start a remote
debugging session. Until I noticed the dialog, I thought the app had hung
on launch. I have to provide a response on every test build before the

app

will run. Also, even if I just relaunch the app after installation, it

asks

again. Basically I can't run the app without replying to the dialog. Is
this correct behavior?

Also, as I mentioned before, if I say "yes" to the dialog, and quit the
app via the Home or App Switcher, there is no message that debugging has
been discontinued. I am pretty sure that's due to the fact that LC

doesn't

send any messages with those keys. At any rate, when that happens, the
scripts can't be edited as they are still in a locked state and I can't
find a way out of that unless I quit and relaunch LC.

What is the expected behavior? There's no toggle to control remote
debugging.

--
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


___
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








--
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

Re: Remote debugging - expected behavior

2017-09-28 Thread J. Landman Gay via use-livecode 
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 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:

http://quality.livecode.com/show_bug.cgi?id=19370

If you think this is not expected behaviour, please file a report for us to
reconsider.

A workaround to prevent the remote debugger from being included in the
standalone is to turn off the wifi in your Android device (or connect to a
different network than the one your machine is connected to). I have not
tested it but I suppose it will work.

Best,
Panos




--
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

Re: Remote debugging - expected behavior

2017-09-28 Thread Mike Kerner via use-livecode 
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 the inclusions when you build, your app is open to
being remote debugged by someone who is not authorized).  I ask here,
rather than adding to that QR or starting a new one, so we can discuss it
before I propose it.

On Thu, Sep 28, 2017 at 3:16 PM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:

> 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:
>
> http://quality.livecode.com/show_bug.cgi?id=19370
>
> If you think this is not expected behaviour, please file a report for us to
> reconsider.
>
> A workaround to prevent the remote debugger from being included in the
> standalone is to turn off the wifi in your Android device (or connect to a
> different network than the one your machine is connected to). I have not
> tested it but I suppose it will work.
>
> Best,
> Panos
> --
>
> On Thu, Sep 28, 2017 at 7:45 PM, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > 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 either.
> >
> > Every time I do a test build, LC asks if I want to start a remote
> > debugging session. Until I noticed the dialog, I thought the app had hung
> > on launch. I have to provide a response on every test build before the
> app
> > will run. Also, even if I just relaunch the app after installation, it
> asks
> > again. Basically I can't run the app without replying to the dialog. Is
> > this correct behavior?
> >
> > Also, as I mentioned before, if I say "yes" to the dialog, and quit the
> > app via the Home or App Switcher, there is no message that debugging has
> > been discontinued. I am pretty sure that's due to the fact that LC
> doesn't
> > send any messages with those keys. At any rate, when that happens, the
> > scripts can't be edited as they are still in a locked state and I can't
> > find a way out of that unless I quit and relaunch LC.
> >
> > What is the expected behavior? There's no toggle to control remote
> > debugging.
> >
> > --
> > 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
> >
> ___
> 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

Re: Remote debugging - expected behavior

2017-09-28 Thread panagiotis merakos via use-livecode 
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:

http://quality.livecode.com/show_bug.cgi?id=19370

If you think this is not expected behaviour, please file a report for us to
reconsider.

A workaround to prevent the remote debugger from being included in the
standalone is to turn off the wifi in your Android device (or connect to a
different network than the one your machine is connected to). I have not
tested it but I suppose it will work.

Best,
Panos
-- 

On Thu, Sep 28, 2017 at 7:45 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> 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 either.
>
> Every time I do a test build, LC asks if I want to start a remote
> debugging session. Until I noticed the dialog, I thought the app had hung
> on launch. I have to provide a response on every test build before the app
> will run. Also, even if I just relaunch the app after installation, it asks
> again. Basically I can't run the app without replying to the dialog. Is
> this correct behavior?
>
> Also, as I mentioned before, if I say "yes" to the dialog, and quit the
> app via the Home or App Switcher, there is no message that debugging has
> been discontinued. I am pretty sure that's due to the fact that LC doesn't
> send any messages with those keys. At any rate, when that happens, the
> scripts can't be edited as they are still in a locked state and I can't
> find a way out of that unless I quit and relaunch LC.
>
> What is the expected behavior? There's no toggle to control remote
> debugging.
>
> --
> 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
>
___
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

Remote debugging - expected behavior

2017-09-28 Thread J. Landman Gay via use-livecode 
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 either.


Every time I do a test build, LC asks if I want to start a remote 
debugging session. Until I noticed the dialog, I thought the app had 
hung on launch. I have to provide a response on every test build before 
the app will run. Also, even if I just relaunch the app after 
installation, it asks again. Basically I can't run the app without 
replying to the dialog. Is this correct behavior?


Also, as I mentioned before, if I say "yes" to the dialog, and quit the 
app via the Home or App Switcher, there is no message that debugging has 
been discontinued. I am pretty sure that's due to the fact that LC 
doesn't send any messages with those keys. At any rate, when that 
happens, the scripts can't be edited as they are still in a locked state 
and I can't find a way out of that unless I quit and relaunch LC.


What is the expected behavior? There's no toggle to control remote 
debugging.


--
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