LiveCode Forums.

Tried watching a variable with a condition in a handler in a card, while running it threw an error in Line number 1 of the card.

Stopped the stack, tried to delete it, no go. Closed stack and removed it from memory, still there, still throwing an error, but possibly at the right line this time - I didn't notice.

Closed out LiveCode, restarted, Windows threw me an error that there was a problem with LiveCode. Restarted, the variable watch was still there, but now I could delete it.

I think I had an error in the placement of my variable watch, I had the watch set for a local variable but before it was assigned a value, and that's why I think it threw an error, but I can't imagine that not being able to delete the watch is normal behavior?

I've seen this when setting a watch on certain script local variables and global variables. There's a bug report about it. Conditional breakpoints set on a script local may have the same problem but I haven't seen that.

You may have better luck using the "remove all breakpoints" menu item in the debug menu if it happens again.

Thanks.

Also tried removing all breakpoints, and it didn't work. The error persisted and the breakpoints were not removed.

In a possibly unrelated problem, I started a new stack after having this problem. The script in that stack wont' run at all. Haven't tried it as a standalone to see if the script will run.

I had 7.0.6 rc-3 and 7.0.5 installed, and uninstalled them both this morning, I wonder if that affected the stable version somehow?

Each version of LC is completely independent, except for the shared preferences file. Sometimes deleting the prefs file helps, but in this case it wouldn't since breakpoints are stored as part of the stack itself. I routinely run three or four different versions of LC simultaneously and none of them interfere with the others. Also, uninstalling/reinstalling LC is almost never necessary. The problem is almost always elsewhere.

Whenever a script won't run at all, I always check the Messages icon in the toolbar to make sure it isn't bolded. Usually that's the problem; I've turned off all messaging so nothing runs. If that's not what's going on, the script may not be in the message path. I can't think of any other reasons it wouldn't run; it should at least try to run and throw an error.