Event

Events in the Tygron Platform are instructions to the software. An event has to be predefined. It will only have an effect when the event is fired. A number of occurrences in the Tygron Platform can cause events to be fired. Examples include the planning and canceling of a measure, or applying an event bundle as an action.

An event has a type and parameters, which specify what the effect of the event is. There are many event types, with many different effects.

Events are very basic instructions for the Tygron Platform to execute. For this reason, they can only be predefined by editors. But by using events, it is possible to make a project more complex and help automate events that occur when activating scenarios.

Where events can be used

Places where events can be triggered are:

• the change of state of measures
• the activation of scenarios
• 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 to let a Stakeholder re-watch a cinematic or to automatically activate multiple measures.

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 project data 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

Editor → Future Design (Ribbon tab) → Event Bundles (Ribbon bar)

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 Future Design.
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 Future Design.
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 Future Design.
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

To learn how to add or remove events from specific project items, refer to their respective articles. For example, if you wish to add an event to a measure, please see the article on measures. Similarly, refer to the relevant element articles to learn how to connect event bundles.

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

---

Future Design

Future Design

Test Run • Actions • Action Menus • Measures • Parametric • Attributes • Levee Types • Upgrade Types • Event Bundles • Active Stakeholders

Actions

Action Logs • Popups • Special Options

Financial

Budget • Cost • Income

Measure

TerrainSpatial • GridSpatial • TiffSpatial • LeveeSpatial • UpgradeSpatial

Editor

Current Situation • Future Design • Multi Scenario • Tools • Community