Re: Remote Debugger Anomalies

Yes, it is part of the repo. https://github.com/trevordevore/levure/tree/master/utils/external_editor_server -- Trevor DeVore ScreenSteps On Mon, Sep 17, 2018 at 9:58 AM Sannyasin Brahmanathaswami via use-livecode wrote: > Do you have that "script acting as a server" available in Levure? > >

Re: Remote Debugger Anomalies

Do you have that "script acting as a server" available in Levure? On 9/17/18 2:31 AM, Trevor DeVore via use-livecode wrote: > When working on a project I always work in ST with the LC IDE open. LC has > a script acting as a server running and ST is the client. ST sends a > notification to LC when

Re: Remote Debugger Anomalies

On Sun, Sep 16, 2018 at 11:54 PM Sannyasin Brahmanathaswami via use-livecode wrote: > > I suppose Trevor would chime here. If you to switch Sublime text and > stay away for SE all together, all the problems go away? Because when > you save the script you know it is in the state of your recent > m

Re: Remote Debugger Anomalies

On 9/16/18 1:38 PM, J. Landman Gay via use-livecode wrote: > Stacks named that way were the ones I tried deleting when the whole IDE > wen I suppose Trevor would chime here. If you to switch Sublime text and stay away for SE all together, all the problems go away? Because when you save the scri

Re: Remote Debugger Anomalies

Stacks named that way were the ones I tried deleting when the whole IDE went down on my next test build. I decided not to do that any more. :) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On September 16, 2018 6:20:13 PM Monte Goulding v

Re: Remote Debugger Anomalies

> On 16 Sep 2018, at 10:36 am, Sannyasin Brahmanathaswami via use-livecode > wrote: > > No doubt Monte is going to say :-) "this is not problem, best you ignore > this" ha!~ This seems a bit unfair to me. I don’t think I’ve ever said that. Clearly if you are having a problem then there’s a p

Re: Remote Debugger Anomalies

> On 16 Sep 2018, at 1:47 am, Sannyasin Brahmanathaswami via use-livecode > wrote: > > OK, given that we understand the problem, to be solved one day. > > Until then, how do we work around it? > > Give an error, and the Script Editor "becomes" > > stack "d2dc63f5-efeb-412c-a6ae-741d60b569de

Re: Remote Debugger Anomalies

Well I play with it a while, I don't have a perfect recipe yet... 1) debug error show up. Do edit the script. You check the error and close the script editor. So far I think the IDE has no cache of it. 2) then on the phone, you go to App Info, Uninstall. So far I didn't get a cached script. But

Re: Remote Debugger Anomalies

I asked this before and the fix is to quit the app, if I remember right. The problem on Android is that apps never really quit, they remain in the background until the OS needs the RAM. When the OS wipes the app, we don't receive any messages so the debugger won't know when the socket closes. Th

Re: Remote Debugger Anomalies

On 9/13/18 10:47 AM, Monte Goulding via use-livecode wrote: > OK that definitely gives me an idea. The cache is meant to be cleaned up when > the socket closes so should be happening between launches of the app but we > can also force the debug session to end during the deploy of the new version

Re: Remote Debugger Anomalies

I made no changes in the second branch, so I deleted it and made a new one from nightly. But, a) since I received a stack from Elanor b) never have opened before c) edit the stack script d) see the stack script of a debug session from Elanor, (Stack name is a usual long ID number) It makes you

Re: Remote Debugger Anomalies

> On 13 Sep 2018, at 11:42 pm, Andrew Bell via use-livecode > wrote: > >> - The stack that caches object scripts is not being cleaned up properly >> between debugging sessions. This would mean that you would see the old >> script but what would be executing would be the new script. One way

Re: Remote Debugger Anomalies

It does not sound like the remote debugger was involved at all in this story so perhaps look elsewhere for the problem. > On 14 Sep 2018, at 6:12 am, Sannyasin Brahmanathaswami via use-livecode > wrote: > > Well this is somewhat "urgent" due to a scenario I just witness. > > It GIT --> branc

Re: Remote Debugger Anomalies

Well this is somewhat "urgent" due to a scenario I just witness. It GIT --> branch -- nightly # scripts updated. committed switch to branch "fixIosBrowser" git merge nightly # get the usual conflict of binary stacks.. git checkout --theirs "view/view_SivaSivaBrowser.livecode" #presumably u

Re: Remote Debugger Anomalies

On 9/13/18 8:42 AM, Andrew Bell via use-livecode wrote: - The stack that caches object scripts is not being cleaned up properly between debugging sessions. This would mean that you would see the old script but what would be executing would be the new script. One way to test this might be to mov

Re: Remote Debugger Anomalies

- The stack that caches object scripts is not being cleaned up properly between debugging sessions. This would mean that you would see the old script but what would be executing would be the new script. One way to test this might be to move a breakpoint statement from one line to another an

Re: Remote Debugger Anomalies

> On 13 Sep 2018, at 5:08 am, J. Landman Gay via use-livecode > wrote: > > I've seen the same thing repeatedly. I wasn't able to work around the > problem. I'd like a way to manually force the debugger to unload itself and > reload the new script. I’d really like to get to the bottom of thi

Re: Remote Debugger Anomalies

I've seen the same thing repeatedly. I wasn't able to work around the problem. I'd like a way to manually force the debugger to unload itself and reload the new script. There is a bug report you can add to: On 9/12/18 8:40 AM, Sannyasin Brah

Re: Remote Debugger Anomalies

Hmm I just go a test stack from Elanor... never open before It has the debug script when she ran it on android saved into SA builder! I went to edit it and get unusual ID 536434756567-36465 (etc.) ? On 9/12/18 3:40 AM, Sannyasin Brahmanathaswami via use-livecode wrote: > -- Shut down LC > -

Remote Debugger Anomalies

-- Shut down LC -- Android phone is connected by USB -- install in app on Android -- fix a script (change a typo) -- save the script; save the stack -- From the test menu, choose Android -- build the app; install on device -- the debugged breaks on the script that I just saved, and it shows the sc