Events as triggers
In the NeuroomNet context, by events we generally mean:
- Messages/signals from components to the NeuroomNet server (such as a motion detector reports movement),
- Changes to global variables defined in NeuroomNet modules.
- Dashboard events (pressing a button, moving a slider)
- Custom events (to trigger a script block from the time control or the dashboard)
In the Script Blocks module, events can be defined as triggers (corresponding to what is meant by a trigger in IT) for the automatic execution of script blocks. Within the script blocks, for example, actions are carried out in components (or component groups).
Example:
A motion detector component registers a movement and reports this event to the NeuroomNet server.
In the script blocks, this component event is defined as a trigger for a script block. The script then switches several other components: e.g. the lighting is changed, sound is played and a video projection is started.
For more information on this, see in particular the chapters Script Blocks and Traffic Inspector.