I actually thought SCENE acted as a getter already, but looking at the docs it doesn’t. It’s not clearly a ‘variable’ as you’re not truly editing that SCENE (but a copy of it), but i think it loosely makes sense
SCENE ADD 1 SCENE
Looks weird for sure, but intuitively I would say this should launch the next numerical SCENE. No new word added & the only logical ‘get’ for
SCENE would be to return the current SCENE.
<edit: apparently this is not what
Then looking at
SCRIPT. Can we think of
SCRIPT as a variable that can be gotten? If so, would this be:
- The most recently executed SCRIPT (
- The script from which it was called (
Are these two options not the same? If
is something different, it should be made clear that which script it refers to isn’t updated until the given script is completed. This could get very confusing if using scripts that call other scripts…
So, maybe we don’t need
THIS, instead use
SCRIPT SCRIPT for recursion, or
STATE SCRIPT would return the trigger high/low state of the executing script.
(as in the last executed script) needs to be sketched out as an alpha feature – it’s the kind of feature that I think needs real world use, not just a does it pass the tests mentality. Perhaps it should only follow physical trigger inputs, or perhaps not. I would like to see people using it IRL to know what the most useful implementation is.