Event

Event

An event is an occurrence or happening. In software specifically, an event is an internal message that something has happened, to which a program can respond.

How events relate to the Tygron Platform

Events in the Tygron Platform are instructions to the software. An event can be defined, but will only have an effect when the event is triggered or "fired". A number of occurrences in the Tygron Platform can cause events to fire. Examples include the planning of a measure, or the answering of a messages.

An event by itself is not yet a specific instruction. An event has a type, and parameters, which specify what the effect of the event is. Because there are many event types, different events can have very different effects.

Events are very basic instructions for the Tygron Platform to execute. For this reason, they can only be defined by editing users. But by using events, it is possible to make a project more complex, and more effective for the participants of a session.

Where events can be used

Places where events can be triggered are:

• the change of state of measures
• the answering of messages
• the activation of levels
• the activation of event bundles

Event Bundles

It is also possible to create event bundles. Event bundles are collections of events that can be triggered as one package. The advantage over loose events is that event bundles can be triggered by multiple sources. Event bundles can be used to trigger events at specific points during a cinematic. Additionally, event bundles can also be added to action menus of stakeholders. This means that it's possible to provide users with an option, solely to fire events. This can be useful when, for example, they must have the ability to set the allowed water level increase for an area, to rewatch a cinematic, or to trigger the sending of a predefined message.

Server events and client events

There are two kinds of events: server events and client events.

Server Events

Main article: Server Events.

Server events are events which are communicated to the server, and may have effects for all stakeholders. An example of this is the activation of a measure. This may affect the 3D world and the indicator scores; changes which are also visible and possibly important to other stakeholders.

Client Events

Main article: Client Events.

Client events are not communicated to the server and and are usually a graphical effect for the stakeholder who triggered the event. Examples of this include flashing an action menu to draw the user's attention, or the visualization of a weather effect.

Adding and removing event bundles

The Left Panel allows you to add, remove, and select event bundles.

You can create (empty) event bundles, which events can then be added to. An event bundle which does not contain events can be used as any other event bundle, but will have no effects.

How to add an event bundle:

1. In the ribbon header, select "Stakeholders".
2. In the ribbon bar, select "Event Bundles".
3. In the left panel, select "Add".

How to duplicate an event bundle:

1. In the ribbon header, select "Stakeholders".
2. In the ribbon bar, select "Event Bundles".
3. In the left panel, select the event bundle you wish to duplicate.
4. In the left panel, select "Duplicate".

How to remove an event bundle:

1. In the ribbon header, select "Stakeholders".
2. In the ribbon bar, select "Event Bundles".
3. In the left panel, select the event bundle you wish to remove.
4. In the left panel, select "Remove".

Adding, removing and editing events

Because events can be added to, and removed from, a number of elements in a project, please see the respective articles on those items for more information on where to add and remove events. For example, if you wish to add an event to a measure, please see the article on measures. Similarly, for information on how to connect event bundles to elements in a project, please see the respective articles on those elements for more information.

For the exact steps for adding, removing, and changing events, please see Editing Events.