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

Reply via email to