On Jul 29, 2019, at 6:14 AM, dunbarxx via use-livecode
wrote:
>
> Do you mean that if you have:
>
> if then breakpoint
No. I mean if I set a condition on the pirate code dots. The first one or
two I set work, at least for the moment, but then they seem to start scarfing
up one anoth
A long time ago I forget which version there was a bug where debug was randomly
turned off and script execution would proceed past hard breakpoints. I haven't
seen that in ages though.
Bob S
> On Jul 29, 2019, at 06:14 , dunbarxx via use-livecode
> wrote:
>
> Hi.
>
> Do you mean that if y
Hi.
Do you mean that if you have:
if then breakpoint
does not fire? The handler proceeds past that line without stopping? Have
you made sure the conditional is valid:
if then answer 'XYZ"
if then breakpoint
Craig
--
Sent from:
http://runtime-revolution.278305.n4.nabble.com/Revolution-U
This is in 9.5-rc1.
I’ve braved tried to use some conditional breakpoints.
However, when it opens one, it seems to show a previously used condition, and
when I replace it, it seems to not get saved, instead remaining blank when I
reopen, and not breaking at all.
Do other people see this?
—
Ri