Breakpoints on a Global

Bob Sneidar bobs at twft.com
Wed Jan 25 12:21:08 EST 2012


Ok I see. When I first clicked next to the variable it was not a global so  that is why when I declared it to a global later it didn't CTD. I went back and checked the watch point and it's scope was the script of the stack. When I set it's scope to global, LC immediately crashes. Sorry for the confusion. 

Bob


On Jan 24, 2012, at 9:28 PM, Mark Wieder wrote:

> Bob Sneidar <bobs at ...> writes:
> 
>> though. This is a feature that used to work. I know because GLX2 used to do
> this successfully. 
> 
> You're confusing breakpoints and watched variables. It used to be that you
> couldn't set a watch on a global variable, but that bug (6506) was fixed in
> version 4.5.2. If you're using PowerDebug for this, just click to the left of
> the global name in the global variables display at the top. If you're using the
> IDE, do whatever (sorry, I can't remember). If you want to do this by script,
> 
> put the watchedvariables into tVars
> put "","",tVariableName,tValue & cr after tVars
> set the watchedvariables to tVars
> 
> where tValue can be empty to match any value
> 
> -- 
> Mark Wieder
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the use-livecode mailing list