Events#
Introduction#
The Events blocks in VEXcode GO allow for event-driven coding, enabling different parts of a project to run in response to triggers such as project start, received events, or user interactions.
Below is a list of available blocks:
when started – Executes the attached stack of blocks when the project starts.
when I receive event – Runs the attached stack when a specific event is broadcast.
broadcast event – Triggers an event without pausing execution.
broadcast event and wait – Triggers an event and pauses execution until the event’s tasks complete.
when started#
The when started block runs its stack when the project begins. You can have multiple when started blocks to run multiple stacks of blocks at once.
when started :: hat events
parameter |
description |
---|---|
This block has no parameters. |
Example
Example coming soon!
when I receive event#
The when I receive event block starts a stack when a matching event is broadcast. You can have multiple when I receive event blocks to run multiple stacks of blocks at once.
when I receive [my_event v]
parameter |
description |
---|---|
event |
The event to be triggered. Users can select an existing event, create a new one, rename the selected event, or delete it. |
Example
Example coming soon!
broadcast event#
The broadcast event block triggers any matching when I receive event hat block. It does not pause the execution of the stack and continues running the next block immediately.
broadcast [message1 v]
parameter |
description |
---|---|
event |
The event to trigger. Users can select an existing event, create a new one, rename the selected event, or delete it. |
Example
Example coming soon!
broadcast event and wait#
The broadcast event and wait block triggers an event, then pauses execution of the current stack until all triggered when I receive event block stacks have completed.
broadcast [message1 v] and wait
parameter |
description |
---|---|
event |
The event to trigger. Users can select an existing event, create a new one, rename the selected event, or delete it. |
Example
Example coming soon!