LiveCode Forums.

Is there a way to get the Variable Watcher stack to update automatically like the VW section below the code? Also the appearance of the VW section is easier to view.

What variable watcher stack do you mean? Is there something other than the Variables pane in the debugger?

Stack "revVariableWatcher"
There is a Context menu at the top where you select the last (lowest) line then the variable values are refreshed.

What LC version are you using? The separate variable watcher window was removed some time before version 6.6.x, which is the oldest version I still have installed. I remember there used to be a Variable Watcher option in the Development window but it was quite a while ago.

I am using Community 7.0.6 recently re-installed. My stacks were originally .REV. Must be some kind of artifact.

I really like using the separate Variable Watcher stack placed to the left of the Code Editor. The Variable Watcher inside the code Editor has a nice easy to use appearance compared to stack "revVariableWatcher" but you have to scroll down from $# past $USERPROFILE to get to your own variables. Awkward even without the lines of $*.

The Global Variables option in Msg would be a good model for an external Variable Watcher.

It would make a good feature request in the QCC.

One trick you simply must try is to hack the script for the variable watcher. This is from Thierry.

Open the script of stack "revdebugger.rev" Find the handler "revDebuggerValidGlobalNames". Place this in its stead:

function revDebuggerValidGlobalNames
local tGlobalsRaw
put the globals into tGlobalsRaw

replace comma with return in tGlobalsRaw

filter tGlobalsRaw without "*(x86)"
filter tGlobalsRaw without "$*"
filter tGlobalsRaw without "grev*"
replace return with comma in tGlobalsRaw

return tGlobalsRaw
end revDebuggerValidGlobalNames

Craig Newman

Wowwwwwww. (10 chars)

Craig,
Thanks for sending that but the code seems to be for another perhaps earlier VW. None of handlers or even code showed up in a search from inside the editor using the Find and More button approach - the most effective in my stacks.

I still use my revVariable stack because it is the most convenient.

Hi.

The name has changed to protect the innocent. Try this:

edit the script of stack "revdebuggerLibrary"

Craig

LiveCode freezes when I paste "*-*" into revDebuggerValidGlobalNames
then try to save. The original script has only these two lines to delete per Thierry:

filter tGlobalsRaw without "*/*" // this I safely commented out.
filter tGlobalsRaw without "*-*" // the culprit. Commenting this out this freezes LC

These are the lines to paste in if I get that far:

filter tGlobalsRaw without "$*"
filter tGlobalsRaw without "grev*"

Can I just paste these in without deleting "*/*" and "*-*"?
What is "grev" all about?
The following globals occur only in stack "revDebuggerLibrary"
global gREVDevelopment
global gREVShowStacks
global gREVSuppressErrors

For that matter, what do
"*/*"
"*-*"
"grev*"
"$*"
actually do?

This all way beyond me but a handy Variable Watcher is so important.

Erik Hansen