Re: breakpoint causes 3 second delay then exit to top

und later that the same thing was happening away from this code block, > and with just a red breakpoint. > > As I don't restart my PC for weeks on end, I quit LC and restarted. Both > of these strange error situations disappeared. Which suggests that it is > some complex con

Re: breakpoint causes 3 second delay then exit to top

I found later that the same thing was happening away from this code block, and with just a red breakpoint. As I don't restart my PC for weeks on end, I quit LC and restarted. Both of these strange error situations disappeared. Which suggests that it is some complex condition (either with

Re: breakpoint causes 3 second delay then exit to top

> Le 17 juil. 2020 à 13:52, Bernard Devlin via use-livecode > a écrit : > > This is mystifying in so many ways. I've seen this a few times and I'm at > a loss to explain it. It's LC 9.5.1 on Windows 10. > > *When the code gets to the above breakpoint, t

breakpoint causes 3 second delay then exit to top

tControlLongId *then* *put* the long time && tControlLongId *breakpoint* *end* *if* *catch* tErr *put* "error:" && tErr *end* *try* *When the code gets to the above breakpoint, the debugger exits to top. It takes about 3 seconds with the debugger sitting

Re: Red Dot Breakpoint Crashes

I *am* truly fascinated that for once, I’m the one not having problems while others are being terrorized by the dreaded Pirate Code Dots . . . . They sill move around the script in odd ways at times, but the ones that stay put do indeed stop execution where they’re supposed to . . . ___

Re: Red Dot Breakpoint Crashes

original dot. Craig -Original Message- From: dunbarx--- via use-livecode To: use-livecode Cc: dunbarx Sent: Sat, Oct 26, 2019 11:14 pm Subject: Re: Red Dot Breakpoint Crashes My red dots are fixed in 9.0.4. Not sure about 9.5, if that might be a regression. Bottom line, I am thrilled th

Re: Red Dot Breakpoint Crashes

. But that hardly recommends the original dot. Craig -Original Message- From: dunbarx--- via use-livecode To: use-livecode Cc: dunbarx Sent: Sat, Oct 26, 2019 11:14 pm Subject: Re: Red Dot Breakpoint Crashes My red dots are fixed in 9.0.4. Not sure about 9.5, if that might be a regressi

Re: Red Dot Breakpoint Crashes

, Oct 25, 2019 10:47 pm Subject: Re: Red Dot Breakpoint Crashes 9.5.1 should have the fix (or whatever it is named). 9.0.5 already has the fix. Thanks, Brian On Oct 25, 2019, 10:44 PM -0400, Paul Looney via use-livecode , wrote: > So, to be fixed in 9.0.6? > > > > On Oct 25, 2019,

Re: Red Dot Breakpoint Crashes

9.5.1 should have the fix (or whatever it is named). 9.0.5 already has the fix. Thanks, Brian On Oct 25, 2019, 10:44 PM -0400, Paul Looney via use-livecode , wrote: > So, to be fixed in 9.0.6? > > > > On Oct 25, 2019, at 6:53 PM, Bob Sneidar via use-livecode > > wrote: > > > > Nope my bad. Not

Re: Red Dot Breakpoint Crashes

So, to be fixed in 9.0.6? > On Oct 25, 2019, at 6:53 PM, Bob Sneidar via use-livecode > wrote: > > Nope my bad. Not fixed in 9.5 yet. > > Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubsc

Re: Red Dot Breakpoint Crashes

Nope my bad. Not fixed in 9.5 yet. Bob S > On Oct 25, 2019, at 16:10 , Tom Glod via use-livecode > wrote: > > any chance you are reading clipboard data? > > On Fri, Oct 25, 2019 at 6:57 PM Mark Wieder via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> On 10/25/19 3:07 PM, Jerr

Re: Red Dot Breakpoint Crashes

any chance you are reading clipboard data? On Fri, Oct 25, 2019 at 6:57 PM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/25/19 3:07 PM, Jerry Jensen via use-livecode wrote: > > Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not > yet put in 9.5 un

Re: Red Dot Breakpoint Crashes

On 10/25/19 3:07 PM, Jerry Jensen via use-livecode wrote: Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not yet put in 9.5 until the next “imminent” release. No? That is correct. -- Mark Wieder ahsoftw...@gmail.com ___ use-liv

Re: Red Dot Breakpoint Crashes

Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not yet put in 9.5 until the next “imminent” release. No? .Jerry > On Oct 25, 2019, at 3:04 PM, Bob Sneidar via use-livecode > wrote: > > 9.5.0 Community. Sorry when it comes to info more is better. Usually. ;-) > Also MacOS Mo

Re: Red Dot Breakpoint Crashes

The reason I think it might be red dot crashing is I have noticed that the red dot is not always in sync with the line it is supposed to be pointing at, typically when scrolling. It seems to correct itself, but then shortly after I saw this while debugging a behavior and switching between execut

Re: Red Dot Breakpoint Crashes

9.5.0 Community. Sorry when it comes to info more is better. Usually. ;-) Also MacOS Mojave fully updated. Bob S > On Oct 25, 2019, at 14:59 , Jerry Jensen via use-livecode > wrote: > > Which version of LC? ___ use-livecode mailing list use-live

Re: Red Dot Breakpoint Crashes

Which version of LC? > On Oct 25, 2019, at 2:28 PM, Bob Sneidar via use-livecode > wrote: > > Still getting red dot breakpoint crashes. This time when switching to the > calling handler. Not a big deal for me just sayi

Red Dot Breakpoint Crashes

Still getting red dot breakpoint crashes. This time when switching to the calling handler. Not a big deal for me just saying. Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and

Re: breakpoint conditions scrambled

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 scarf

Re: breakpoint conditions scrambled

gt; 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 __

Re: breakpoint conditions scrambled

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/

breakpoint conditions scrambled?

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

Re: Breakpoint

Sep 18, 2017, at 11:21 , Jean-Jacques Wagner via use-livecode > wrote: > > Hallo > Still working with on 6.7.7 but experiencing a lot of troubles with > breakpoint, can’t set, have to activate before each run otherwise don’t > trigger. Script debugging become a nightmare.

Breakpoint

Hallo Still working with on 6.7.7 but experiencing a lot of troubles with breakpoint, can’t set, have to activate before each run otherwise don’t trigger. Script debugging become a nightmare. I’ll never have seen such a bad behavior. Does anyone nows how to circumvent this missbehavior. Jean

Re: breakpoint on parameter

created, but then it turns gray. I can't find the script | > that's turning it gray. | > | > I don't know where to put a breakpoint in the script. | > | > Can I put a breakpoint on that control's color parameter, so execution | > stops whenever something modifi

Re: breakpoint on parameter

On 05/24/2017 08:23 AM, Mark Waddingham via use-livecode wrote: Right now, though there might be a way in the IDE by using an IDE mechanism - the IDE has an API allowing an object to subscribe to a message when any properties of that object change: revIDESubscribe "idePropertyChanged", T

Re: breakpoint on parameter

y. I can't find the script that's turning it gray. I don't know where to put a breakpoint in the script. Can I put a breakpoint on that control's color parameter, so execution stops whenever something modifies it and goes to the script that's doing the modification? There&

Re: breakpoint on parameter

On 2017-05-23 17:57, Mark Wieder via use-livecode wrote: On 05/23/2017 08:45 AM, Richard Gaskin via use-livecode wrote: There's a request to allow getProp and setProp for built-in object properties: http://quality.livecode.com/show_bug.cgi?id=3126 ...and it's from 2005, rev version 2.6...

Re: breakpoint on parameter

On Tue, May 23, 2017 at 3:39 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > (There are ways to break when certain variables change but that's > different.) Has that bug ever been fixed? I never found the IDE crashing a useful way to debug :) -- Dr. Richard E. H

Re: breakpoint on parameter

nd the script that's turning it gray. I don't know where to put a breakpoint in the script. Can I put a breakpoint on that control's color parameter, so execution stops whenever something modifies it and goes to the script that's doing the modification? You can't break for a

Re: breakpoint on parameter

On 05/23/2017 08:45 AM, Richard Gaskin via use-livecode wrote: There's a request to allow getProp and setProp for built-in object properties: http://quality.livecode.com/show_bug.cgi?id=3126 ...and it's from 2005, rev version 2.6... -- Mark Wieder ahsoftw...@gmail.com

Re: breakpoint on parameter

7;s turning it gray. > > I don't know where to put a breakpoint in the script. > > Can I put a breakpoint on that control's color parameter, so execution > stops whenever something modifies it and goes to the script that's > doing the modification? There's a

breakpoint on parameter

I want to find out which parts of my code are making changes to a control's parameter. Specifically, I've got an arrow that I want to be black, and it is black when it's created, but then it turns gray. I can't find the script that's turning it gray. I don't know wh

Re: Unable to set breakpoint

Gremlins. Bob S > On May 9, 2017, at 20:02 , J. Landman Gay via use-livecode > wrote: > > How come things only fall apart when I'm in a crunch? > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com ___ use-livecode mailing list

Re: Unable to set breakpoint

On 5/9/17 2:55 PM, Mark Wieder via use-livecode wrote: Here's what I found earlier with the preferences files: Very helpful, thanks. It will save me some trouble next time. How come things only fall apart when I'm in a crunch? -- Jacqueline Landman Gay | jac...@hyperactivesw.com

Re: Unable to set breakpoint

On 05/09/2017 12:55 PM, Mark Wieder via use-livecode wrote: On 05/09/2017 07:32 AM, J. Landman Gay via use-livecode wrote: I do still have an old pre-7 prefs file in the same folder as the new one, since I need to open LC 6 occasionally. It may be that LC 9 couldn't read or update it so it just

Re: Unable to set breakpoint

On 05/09/2017 07:32 AM, J. Landman Gay via use-livecode wrote: I do still have an old pre-7 prefs file in the same folder as the new one, since I need to open LC 6 occasionally. It may be that LC 9 couldn't read or update it so it just gave up. Here's what I found earlier with the preferences

RE: Unable to set breakpoint

...@lists.runrev.com] On Behalf Of J. Landman Gay via use-livecode Sent: Tuesday, May 09, 2017 1:16 PM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: Unable to set breakpoint On 5/9/17 10:06 AM, panagiotis merakos via use-livecode wrote: > It would be interesting to know which Plugins

Re: Unable to set breakpoint

On 5/9/17 10:06 AM, panagiotis merakos via use-livecode wrote: It would be interesting to know which Plugins you and Ralph have in common. Only one, LiveCode Error Lookup, which does nothing until you manually open it. I've got these: 4W_FlightRecorder.rev 4W_gzipper.livecode AirLaunch.livec

RE: Unable to set breakpoint

...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of panagiotis merakos via use-livecode Sent: Tuesday, May 09, 2017 11:07 AM To: How to use LiveCode Cc: panagiotis merakos Subject: Re: Unable to set breakpoint I had LC 6 Prefs too, but did

RE: Unable to set breakpoint

use LiveCode Cc: J. Landman Gay Subject: Re: Unable to set breakpoint Panos, it wasn't just the tools palette, there was no IDE at all. There were no menus except for the default OS X one that allowed me to quit. Nothing else loaded, so no message box, tools, keyboard shortcuts, etc. It

Re: Unable to set breakpoint

;>> Ralph DiMola >>> IT Director >>> Evergreen Information Services >>> rdim...@evergreeninfo.net >>> >>> -Original Message- >>> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On >>> Behalf >>> Of

Re: Unable to set breakpoint

net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of J. Landman Gay via use-livecode Sent: Monday, May 08, 2017 5:03 PM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: Unable to set breakpoint Thanks, I hadn't thought of that

Re: Unable to set breakpoint

use-livecode wrote: Have you tried deleting your Prefs? On Mon, May 8, 2017 at 9:49 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints are dimmed as though the script has not been compiled (it h

Re: Unable to set breakpoint

green Information Services > rdim...@evergreeninfo.net > > -Original Message- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On > Behalf > Of J. Landman Gay via use-livecode > Sent: Monday, May 08, 2017 5:03 PM > To: How to use LiveCode > C

RE: Unable to set breakpoint

riginal Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of J. Landman Gay via use-livecode Sent: Monday, May 08, 2017 5:03 PM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: Unable to set breakpoint Thanks, I hadn't thought of that. I tried

Re: Unable to set breakpoint

gt; wrote: >>> >>> Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints >>>> are dimmed as though the script has not been compiled (it has, several >>>> times.) Hard-coded "breakpoint" commands to not trigger either. I am not >>

Re: Unable to set breakpoint

code < use-livecode@lists.runrev.com> wrote: Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints are dimmed as though the script has not been compiled (it has, several times.) Hard-coded "breakpoint" commands to not trigger either. I am not able to debug. Th

Re: Unable to set breakpoint

(it has, several times.) Hard-coded "breakpoint" commands to not trigger either. I am not able to debug. Things were going along well until I allowed remote debugging. That worked for a while, then I got several crashes in a row, and now I can't set breakpoints. I have retarted LC se

Re: Unable to set breakpoint

17 at 9:49 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints are dimmed as though the script has not been compiled (it has, several times.) Hard-coded "breakpoint" commands to n

Re: Unable to set breakpoint

you tried deleting your Prefs? On Mon, May 8, 2017 at 9:49 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints are dimmed as though the script has not been compiled (it has, several times.) Hard-c

Re: Unable to set breakpoint

eral > times.) Hard-coded "breakpoint" commands to not trigger either. I am not > able to debug. > > Things were going along well until I allowed remote debugging. That worked > for a while, then I got several crashes in a row, and now I can't set > breakpoints. >

Unable to set breakpoint

Suddenly I have lost the ability to set breakpoints. Red-dot breakpoints are dimmed as though the script has not been compiled (it has, several times.) Hard-coded "breakpoint" commands to not trigger either. I am not able to debug. Things were going along well until I allowed remote

Re: BreakPoint problems in LC8DP10

ttp://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Thu, Dec 3, 2015 at 1:33 PM, William Prothero wrote: > I thought breakpoint problems were solved in DP10 and hoped to transfer to > LC8 permanently, but there seems to still be a problem. >

Re: BreakPoint problems in LC8DP10

Thanks, Peter” That’s most likely it. I hope to get a version of LC8 that I can actually use, soon. Best, Bill > On Dec 3, 2015, at 1:37 PM, Peter TB Brett wrote: > > On 2015-12-03 21:33, William Prothero wrote: >> I thought breakpoint problems were solved in DP10 and hoped to

Re: BreakPoint problems in LC8DP10

On 2015-12-03 21:33, William Prothero wrote: I thought breakpoint problems were solved in DP10 and hoped to transfer to LC8 permanently, but there seems to still be a problem. I do a: dispatch “myHandlerName" to grp “MygroupName” There is a breakpoint in the handler “myHandlerName

BreakPoint problems in LC8DP10

I thought breakpoint problems were solved in DP10 and hoped to transfer to LC8 permanently, but there seems to still be a problem. I do a: dispatch “myHandlerName" to grp “MygroupName” There is a breakpoint in the handler “myHandlerName” The handler is in the script of thegroup “myGrou

Re: "breakpoint" gets edited out of cut/paste in IDE?

een copying and pasting scripts with breakpoints from the Rev 2.0 days and have never noticed this ever happening. I just did a quick test in 2 new stacks in 7.0.5 and had not problem copying a script with a hard breakpoint across to the other stack. On Fri, Jun 5, 2015 at 7:09 AM, Dr. Hawkins wrote

"breakpoint" gets edited out of cut/paste in IDE?

has anyone else seen this? If I copy a block of if sGrp="p13_6.0.1" then breakpoint end if in the IDE, and then paste it elsewhere in the IDE, the middle line with breakpoint is consistently not appearing, with instead a blank line. Has anyone else seen something

Re: Weird glitch in breakpoint behavior

On 5/24/13 12:09 AM, dunb...@aol.com wrote: Hi.. I don't see this. I assume you meant "LiveCode/Preferences", not "Edit/Preferences"? Anyway, I can open the preferences stack while the script is stopped at line 2, dismiss the stack and find myself still at line 2. From there I can step or run

Re: Weird glitch in breakpoint behavior

Hi.. I don't see this. I assume you meant "LiveCode/Preferences", not "Edit/Preferences"? Anyway, I can open the preferences stack while the script is stopped at line 2, dismiss the stack and find myself still at line 2. From there I can step or run the script. Nothing untoward. Craig Newman

Weird glitch in breakpoint behavior

I was testing a 6.0.1 stack when "Step into next statement" after a manual breakpoint acted like a 'Continue" ... meaning it didn't stop until the end of the script. I was able to recreate the problem repeatedly, so I began to whittle down my script to find what caused

Re: an ignored breakpoint

On Mon, Sep 10, 2012 at 7:48 PM, Kay C Lan wrote: > Lets be thankful Revolution has progressed to LiveCode. I don't think I > skinned any cats with 1.1. I skinned a lot with Hypercard 1 & 2, and Supercard 1.5, though . . . and if either SuperCard or Revolution had come out by early 94 for the pc,

Re: an ignored breakpoint

Lets be thankful Revolution has progressed to LiveCode. I don't think I skinned any cats with 1.1. On Tue, Sep 11, 2012 at 12:49 AM, Bob Sneidar wrote: > Let us be thankful that most of us live in a place unlike Africa, where > the cats can skin us! > > On Sep 9, 2012, at 5:14 PM, Dr. Hawkins wr

Re: an ignored breakpoint

Let us be thankful that most of us live in a place unlike Africa, where the cats can skin us! On Sep 9, 2012, at 5:14 PM, Dr. Hawkins wrote: >> LiveCode - an ever-increasing number of ways to skin each cat. > > None of which, however, yield a happy cat . . . __

Re: an ignored breakpoint

On Fri, Sep 7, 2012 at 1:47 AM, Ben Rubinstein wrote: > LiveCode - an ever-increasing number of ways to skin each cat. -- The Hawkins Law Firm Richard E. Hawkins, Esq. (702) 508-8462 hawkinslawf...@gmail.com 3025 S. Maryland Parkway Suite A Las Vegas, NV 89109 ___

Re: an ignored breakpoint

On Thu, Sep 6, 2012 at 12:51 PM, Bob Sneidar wrote: > Another thing to watch out for is setting breakpoints with variable values. > This in >the past would crash LC. I'm not sure if they fixed it yet. I was crashing all >the time >once and thought it was a really unstable build, until I realized

Re: an ignored breakpoint

On 07/09/2012 09:13, Kay C Lan wrote: Clearly I need to wean myself back to using the occasional Red Dot. LiveCode - an ever-increasing number of ways to skin each cat. Ben ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit thi

Re: an ignored breakpoint

Ben, Thanks for the pointer. No I certainly didn't know about the Breakpoint tab - well for some strange reason it doesn't do anything for hard coded breakpoints, when I click on the Tab it comes up empty so I guess I've occasionally clicked on it and have come away assuming

Re: an ignored breakpoint

Another thing to watch out for is setting breakpoints with variable values. This in the past would crash LC. I'm not sure if they fixed it yet. I was crashing all the time once and thought it was a really unstable build, until I realized I had set and forgot about a variable watch point. Bob

Re: an ignored breakpoint

There's certainly a need to set "markers" of various sorts in scripts and the best tool to do this is Bill Vlahos' lcTaskList, available on the RunRev store for $10. Pete lcSQL Software On Thu, Sep 6, 2012 at 1:26 AM, Ben Rubinstein wrote: > On 06/09/2012 02:09, Kay C

Re: an ignored breakpoint

Lan wrote:> One thing I like a lot about breakpoints is I can quickly and easily turn On and Off all/selected breakpoints in all/selected scripts using Find and Replace. Find 'breakpoint' Replace with '--breakpoint' and vice versa. I don't even have to type it, because

Re: an ignored breakpoint

breakpoints I simply turn Off Script Debug Mode. One thing I like a lot about breakpoints is I can quickly and easily turn On and Off all/selected breakpoints in all/selected scripts using Find and Replace. Find 'breakpoint' Replace with '--breakpoint' and vice versa. I don

Re: an ignored breakpoint

On 9/5/12 8:09 PM, Kay C Lan wrote: I do miss the Trace option we used to have, and because of that I do liberally sprinkle 'breakpoint' throughout my code. I could have 6-12 breakpoints across half a dozen handlers/functions across a 1000 lines of code. I couldn't imagine findin

Re: an ignored breakpoint

On Wed, Sep 5, 2012 at 12:14 AM, Peter Haworth wrote: > I'm surprised by the number of problems people are reporting with the > debugger. > Since using 'breakpoint' exclusively I've not experienced any problems with the debugger; but then again I don't

Re: an ignored breakpoint

I have had the debugger ignore a specifically written 'breakpoint' in a script some time ago, but it was a bug and has since been fixed. Bob On Sep 2, 2012, at 12:07 AM, Kay C Lan wrote: >> If I don't have the breakpoint, but instead reddot the "if isdna"

Re: an ignored breakpoint

On 9/4/12 11:14 AM, Peter Haworth wrote: I'm surprised by the number of problems people are reporting with the debugger. Not to say I've never had any but they are now few and far between. The one thing I do see consistently is ignoring a red dot breakpoint in preOpenCard. Most of

Re: an ignored breakpoint

I'm surprised by the number of problems people are reporting with the debugger. Not to say I've never had any but they are now few and far between. The one thing I do see consistently is ignoring a red dot breakpoint in preOpenCard. Most of the time a hard coded breakpoint works, but

Re: an ignored breakpoint

On 9/4/12 8:05 AM, Bernard Devlin wrote: However, I've seen a pattern to reddot breakpoints being ignored. Once a script has run through with a reddot, on a subsequent run the reddot is ignored (unless the script is re-saved between executions). I only see that if the script has been edited b

Re: an ignored breakpoint

I've almost never used the "breakpoint" command; it's too cumbersome (or I'm too lazy). However, I've seen a pattern to reddot breakpoints being ignored. Once a script has run through with a reddot, on a subsequent run the reddot is ignored (unless the script is re-

Re: an ignored breakpoint

On 9/2/12 11:31 AM, Dr. Hawkins wrote: On Sun, Sep 2, 2012 at 12:07 AM, Kay C Lan wrote: IMO the red dots are like the Geometry Manager - to be avoided because they are flaky. YEah, but they can be added to a running script. I almost never need to insert a breakpoint command, so your

Re: an ignored breakpoint

On 9/1/12 12:24 PM, Dr. Hawkins wrote: Saw another one just now. A loop ends: end switch put ", " & theField & "=" & theDat after updStr --if theFIeld="due" then exit repeat end repeat breakpoint if isDna then I

Re: an ignored breakpoint

On Sun, Sep 2, 2012 at 12:07 AM, Kay C Lan wrote: > IMO the red dots are like the Geometry Manager - to be avoided because they > are flaky. YEah, but they can be added to a running script. >I've never had the debugger ignore a specifically written > 'breakpoint' in

Re: an ignored breakpoint

On Sun, Sep 2, 2012 at 1:24 AM, Dr. Hawkins wrote: > > If I don't have the breakpoint, but instead reddot the "if isdna", the > breakpoint is ignored. > IMO the red dots are like the Geometry Manager - to be avoided because they are flaky. I've never had th

an ignored breakpoint

Saw another one just now. A loop ends: end switch put ", " & theField & "=" & theDat after updStr --if theFIeld="due" then exit repeat end repeat breakpoint if isDna then If I don't have the breakpoint, but instead r