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-livecode<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