In the default debugger you can select the Breakpoints in the lower tab. Then right-click and select New Watch. Select Global Scope in the Handler popup. Select a global variable in the Variable popup. Set a condition (or no it doesn't matter). Click OK. Crash to desktop. DISCLAIMER: Save your changes to all open stacks first!!! :-)
Note that it will only CTD if the variable exists. I still have a watch set for a global in my test stack and have had all morning and it hasn't crashed. That may help whoever at RR to troubleshoot it. If I knew where in the library this was handled I would troubleshoot it myself! Bob On Jan 25, 2012, at 11:14 AM, J. Landman Gay wrote: > On 1/24/12 11:28 PM, Mark Wieder wrote: > >> 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). > > In the IDE, you set a breakpoint and then edit it to set a watch, so they > look the same there, basically. > > -- > 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 _______________________________________________ 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
