If you read the User's Guide, you'll see that Globals can be used in Expressions
It is quite the expansive document and in general help information in both the guide and the interface is TOP NOTCH, and for that I am very very grateful.
I reference it often, and I use globals in expressions all the time!
I'll start a thread on resetting ramps and other things, because it's too far OT and the tip about disabling downstream modules is
super helpful, and I still have another question in that vein.
but why would you want that?
Back to original topic - I'll try 2 other examples
a) I have an OSC button on a device. When I push that button it sends a value of 1 through the pipe at /button . It's not a toggle, it doesn't have an up/down value - it can only send a value of 1 when it is pushed. I want that to bang the Goto Start on a video. Or I want that to increase the Index on a JpegFolder by 1 each push. The value is always 1.0, but that 1.0 is getting re-sent on OSC.
b) I have a MIDI knob in continuous mode. It sends 0 when turned left, and 1 when turned right. The more left it is turned, the more 0's are sent down the pipe. The more right it is turned the more 1's are sent down the pipe. So If I'm turning right, I want a global or module parameter to continue increasing each time it gets the event for as long as I'm turning, but not continue increasing when I'm not turning. You can use Increase (Linear) - set to 0.0 - to accumulate a value, but that won't work because the last sent value was a 1, even though it's not sending that event any longer.
Also, the Playlist will respond this way to events: If you send the same value for the same parameter, it still restarts the same scene.