IDE property 'the watchedVariables' ?
Posted: Sat Jul 09, 2022 11:19 am
I've pulled the variable watcher stack from LCC v.8.1.10 into OXT.
Apparently this stack was removed in v.9.x
Examining the scripts I see there is an undocumented IDE property called the watchedVariables.
Does anybody know anything about this property?
'put the watchedVariables' -- puts empty...
set the watchedVariables to "anExistingVariableName" -- throws 'not a container'
Perhaps the IDE needs to be in 'debug' mode (IDE "debug" mode as opposed to 'development' mode) for that to be used?
Also in v8 (but not in v.9) I found there is a stack called 'revtemplatechooser.rev' that doesn't appear to be functional anymore. I would definitely like to have something like that, pre-built starter template stacks for a variety of use cases. This is one of the uses I had in mind for that XML or other markup text-based UI pseudo-stack format as an expansion on the 'script-only' stack format (which doesn't allow for graphics).
This is NOT distraction!
I found these while looking to correct the behavior of clicks on windows that occlude or are above the bottom of the "revMenuBar" stack.
Apparently this stack was removed in v.9.x
Examining the scripts I see there is an undocumented IDE property called the watchedVariables.
Does anybody know anything about this property?
'put the watchedVariables' -- puts empty...
set the watchedVariables to "anExistingVariableName" -- throws 'not a container'
Perhaps the IDE needs to be in 'debug' mode (IDE "debug" mode as opposed to 'development' mode) for that to be used?
Also in v8 (but not in v.9) I found there is a stack called 'revtemplatechooser.rev' that doesn't appear to be functional anymore. I would definitely like to have something like that, pre-built starter template stacks for a variety of use cases. This is one of the uses I had in mind for that XML or other markup text-based UI pseudo-stack format as an expansion on the 'script-only' stack format (which doesn't allow for graphics).
This is NOT distraction!
I found these while looking to correct the behavior of clicks on windows that occlude or are above the bottom of the "revMenuBar" stack.