Breakpoints on a Global

[Bob Sneidar]

Oddly, watchedVariables is not in the dictionary. I created a new stack, set a global in the stack script, created an Openstack handler, set a breakpoint in the first line of the handler, and changed the value of the global twice, once to empty and once to a string of text. I ran OpenStack and while powerDebugger was open I clicked next to the global variable setting a watch on it. As soon as the global value is changed Livecode crashes to desktop. This happens regardless of whether or not it is an array, so that has nothing to do with it. If the variable is NOT a global, LC does NOT crash to desktop. 

If this was fixed in 4.5, then it's broke again. 

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