> On 1 Nov 2017, at 1:45 pm, J. Landman Gay via use-livecode
> wrote:
>
>> Once you hit a breakpoint you should be able to change breakpoints in the
>> open debugger.
>
> This I didn't know, I wasn't able to do that. To verify: I have to be stopped
> at a breakpoint first before changing or
On 10/31/17 4:14 PM, Monte Goulding via use-livecode wrote:
Once you hit a breakpoint you should be able to change breakpoints in the open
debugger.
This I didn't know, I wasn't able to do that. To verify: I have to be
stopped at a breakpoint first before changing or adding one? I didn't do
> On 31 Oct 2017, at 9:15 pm, Peter Reid via use-livecode
> wrote:
>
> How are people getting on with the remote debugger facility? I'm finding it
> very useful but also frustrating for the following reasons:
>
> 1. It's SLOW. I'm running LC 9 on an iMac with a 4GHz quad i7 processor and
> 2
On 10/31/17 5:15 AM, Peter Reid via use-livecode wrote:
3. Often it steps through the script as it was just before the latest change,
i.e. it doesn't take into account the latest script edits.
4. It can be difficult to change break points during remote debugging.
You need to recompile/rebuild
