A recent article in the Digital Newsletter covered the use of the LOOP Macro , one of the Advanced Event functions
A single dismissive comment was made that the looping, once started could not be stopped
I consider this far too important an oversight to go unchallenged, and offer the following for discussion.
The first image below shows a Macro LOOP operation that calls the RANDOM macro every two seconds to alter the colour of a 3 aspect indicator
As shown ,this will indeed run forever once started.
However an aspect of the LOOP container is that any sensor(control) that is placed within the sequence can act as a circuit breaker to stop the looping
As you may observe, the editing of the sensor within this specific function has no other cabability to set an action or delay, these are greyed out.
FWIW, you may have multiple sensor(controls) defined and any one of them would stop the looping 
In practice I might suggest using an on/off switch that, when turned on, triggers the loop to commence.
The looping tests the switch each cycle and will continue looping as long as the switch is on.
Turning the switch off will cause the test of the sensor to fail and the looping to stop.
To cover off other means to stop an endless loop
- The "Control" button on the events screen offers functions to Block, Terminate and Stop Events
- If needed the "Stop Event" function can be called as an event instruction itself (just like the Stop, Go and Halt)
For those new to the CS3 and advanced events, this is an area of the software that works well once setup.
However the CS3 can get its brains mixed up if you do a lot of edits, adds and deletes along the way.
If something seems odd, reboot.
Edited by user 11 June 2020 00:35:30(UTC)
| Reason: Not specified
