Re: an ignored breakpoint
On Mon, Sep 10, 2012 at 7:48 PM, Kay C Lan lan.kc.macm...@gmail.com 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, my program might have hit the market 20 years ago . . . some things it did then are still ahead of today's competition! -- The Hawkins Law Firm Richard E. Hawkins, Esq. (702) 508-8462 hawkinslawf...@gmail.com 3025 S. Maryland Parkway Suite A Las Vegas, NV 89109 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 . . . ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 b...@twft.com 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 wrote: LiveCode - an ever-increasing number of ways to skin each cat. None of which, however, yield a happy cat . . . ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: an ignored breakpoint
On Thu, Sep 6, 2012 at 12:51 PM, Bob Sneidar b...@twft.com 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 I had set and forgot about a variable watch point. Conditional breakpoints work. Just don't try a variable watch . . . . On Fri, Sep 7, 2012 at 1:47 AM, Ben Rubinstein benr...@cogapp.com wrote: LiveCode - an ever-increasing number of ways to skin each cat. None of which, however, yield a happy 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 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: an ignored breakpoint
On Fri, Sep 7, 2012 at 1:47 AM, Ben Rubinstein benr...@cogapp.com 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 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 it's telling me nothing. Clearly I need to wean myself back to using the occasional Red Dot. Thanks. On Thu, Sep 6, 2012 at 4:26 PM, Ben Rubinstein benr...@cogapp.com wrote: I appreciate you've had trouble with red dots - and that you also mentioned some other factors you appreciate about 'breakpoint', eg persistence - but I thought that since you've evidently not used red dots for a while you may not have noticed that the script editor now has a 'Breakpoints' tab which tracks all the red dots in all scripts/stacks. From here you can delete, or enable/disable each one without deleting it and can edit the condition on each - and can also double-click to go directly to that line of code, opening the relevant script if required. (So I suppose disabled breakpoints could be used as a kind of bookmark.) This area also provides access to variable watches if you use those (I hadn't realised until just now that we had this facility!). Apologies if you already knew this. On the other hand, I only just learnt from your emails that I could switch off Script Debug Mode to disable all hard-coded 'breakpoint' statements! Ben __**_ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: an ignored breakpoint
On 06/09/2012 02:09, Kay C Lan wrote: I could have 6-12 breakpoints across half a dozen handlers/functions across a 1000 lines of code. I couldn't imagine finding and resetting all of those, just to ensure they worked, if I used 'red dots' instead. On 06/09/2012 04:45, Kay C 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 I've done it before those strings appear in the option buttons in the Find and Replace window. It then also makes it very easy to reinstate some/all breakpoints. Hi Kay I appreciate you've had trouble with red dots - and that you also mentioned some other factors you appreciate about 'breakpoint', eg persistence - but I thought that since you've evidently not used red dots for a while you may not have noticed that the script editor now has a 'Breakpoints' tab which tracks all the red dots in all scripts/stacks. From here you can delete, or enable/disable each one without deleting it and can edit the condition on each - and can also double-click to go directly to that line of code, opening the relevant script if required. (So I suppose disabled breakpoints could be used as a kind of bookmark.) This area also provides access to variable watches if you use those (I hadn't realised until just now that we had this facility!). Apologies if you already knew this. On the other hand, I only just learnt from your emails that I could switch off Script Debug Mode to disable all hard-coded 'breakpoint' statements! Ben ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 http://www.lcsql.com On Thu, Sep 6, 2012 at 1:26 AM, Ben Rubinstein benr...@cogapp.com wrote: On 06/09/2012 02:09, Kay C Lan wrote: I could have 6-12 breakpoints across half a dozen handlers/functions across a 1000 lines of code. I couldn't imagine finding and resetting all of those, just to ensure they worked, if I used 'red dots' instead. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 On Sep 6, 2012, at 12:19 PM, Peter Haworth wrote: 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 http://www.lcsql.com On Thu, Sep 6, 2012 at 1:26 AM, Ben Rubinstein benr...@cogapp.com wrote: On 06/09/2012 02:09, Kay C Lan wrote: I could have 6-12 breakpoints across half a dozen handlers/functions across a 1000 lines of code. I couldn't imagine finding and resetting all of those, just to ensure they worked, if I used 'red dots' instead. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 finding and resetting all of those, just to ensure they worked, if I used 'red dots' instead. One thing I like a lot about the red dots is that you can remove all of them from all scripts with a single menu item selection Clear all breakpoints. Very handy. I haven't had much trouble with the red dots. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: an ignored breakpoint
On Thu, Sep 6, 2012 at 9:31 AM, J. Landman Gay jac...@hyperactivesw.comwrote: One thing I like a lot about the red dots is that you can remove all of them from all scripts with a single menu item selection Clear all breakpoints. Very handy. If I want to test my scripts without ANY 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't even have to type it, because I've done it before those strings appear in the option buttons in the Find and Replace window. It then also makes it very easy to reinstate some/all breakpoints. Again, I liked the old Trace, and some of what I do is because I can't Trace any more, so with a bit of trial and error I'll find the right place to put a breakpoint, attempt to figure out what's wrong, and when I think I've got it right I'll just comment it out. Days/weeks.months/years later when under unforeseen circumstances I hit basically the same error I know exactly where to put the breakpoint because it's sitting there waiting to be uncommented. I like that during development I can leave place holders at important locations in my script and long after I've forgotten why they are important I can come back, uncomment them, then step through my code to each important location at which point the reason for the current problem I'm trying to troubleshoot usually becomes immediately apparent - unfortunately the code required to correct the deficit normally takes a whole lot longer to nut out and incorporate ;-) ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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-saved between executions). So, when I have worked on a particular piece of code, I disable/re-enable the reddot between executions (unless I've edited the code in between). It's tiresome, but less tiresome then using the breakpoint command. I think also that certain livecode formatting (e.g. if I remember correctly, one line if-thens), can cause mischief. Bernard On Mon, Sep 3, 2012 at 6:33 PM, J. Landman Gay I almost never need to insert a breakpoint command, so your mileage may vary. The red dots don't always work, but for me they do most of the time. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 but not saved. On subsequent runs, the engine will be executing the older version and the dot may not align with a valid break point. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 not always. A good number of the other weirdnesses I've seen have turned out to be indications of problems in my code. The mysterious jumping ahead several lines of code after a breakpoint is now an indication to me that a call to rev Library routine has a problem of some sort, perhaps an alpha value where a numeric value is expected or a missing parameter. I've also learned to avoid setting breakpoints in some message handlers, notably ones that deal with mouse movement, especially if I'm looking at the mouseLine or the mouseCharchunk. I also found recently that setting a breakpoint in a resizeStack handler froze the IDE, at least until I found I could use the keyboard equivalents of stepover, step through, etc. Pete lcSQL Software http://www.lcsql.com On Tue, Sep 4, 2012 at 6:05 AM, Bernard Devlin bdrun...@gmail.com wrote: 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-saved between executions). So, when I have worked on a particular piece of code, I disable/re-enable the reddot between executions (unless I've edited the code in between). It's tiresome, but less tiresome then using the breakpoint command. I think also that certain livecode formatting (e.g. if I remember correctly, one line if-thens), can cause mischief. Bernard On Mon, Sep 3, 2012 at 6:33 PM, J. Landman Gay I almost never need to insert a breakpoint command, so your mileage may vary. The red dots don't always work, but for me they do most of the time. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 the time a hard coded breakpoint works, but not always. A good number of the other weirdnesses I've seen have turned out to be indications of problems in my code. The mysterious jumping ahead several lines of code after a breakpoint is now an indication to me that a call to rev Library routine has a problem of some sort, Exactly my experience too. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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, the breakpoint is ignored. IMO the red dots are like the Geometry Manager - to be avoided because they are flaky. I've never had the debugger ignore a specifically written 'breakpoint' in a script, so that's what I ALWAYS use. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 If I don't have the breakpoint, but instead reddot the if isdna, the breakpoint is ignored. If you can post (or send me) the full handler I can test it. My guess is that something above the section you posted is the problem, but it's hard to say. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 lan.kc.macm...@gmail.com 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 mileage may vary. The red dots don't always work, but for me they do most of the time. I've never had the debugger ignore a specifically written 'breakpoint' in a script, so that's what I ALWAYS use. I have yet to get one to work in preOpenStack (at least for the main stack) unless I precede it with an answer . . . The preOpen-everythings on the first card are the main occasion where I do need to insert a scripted breakpoint. Those work if the stack is opened from within the IDE. Double-clicking the stack to launch the IDE doesn't always break; I always thought the debugger wasn't available yet when that happens. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: an ignored breakpoint
On Sun, Sep 2, 2012 at 12:07 AM, Kay C Lan lan.kc.macm...@gmail.com 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 a script, so that's what I ALWAYS use. I have yet to get one to work in preOpenStack (at least for the main stack) unless I precede it with an answer . . . -- The Hawkins Law Firm Richard E. Hawkins, Esq. (702) 508-8462 hawkinslawf...@gmail.com 3025 S. Maryland Parkway Suite A Las Vegas, NV 89109 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
