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
Yes long standing issue ever since v9 I believe. Might have been since v7. I
have to do the same thing. Apparently copies of things like library stacks (not
the originals, but the COPIES created when building a standalone) are left open
in memory. Not sure why they do that. Anything opened in th
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 all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #187 here: http://bit.ly/2Mnylcc
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
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
