Event: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Events in the {{software}} are instructions to the software. An event | Events in the {{software}} 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 {{software}} can cause events to be fired. Examples include the planning and canceling of a [[measures|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 {{software}} to execute. For this reason, they can only be | Events are very basic instructions for the {{software}} to execute. For this reason, they can only be predefined by [[User#Editor|editing users]]. 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== | ==Where events can be used== | ||
Places where events can be triggered are: | Places where events can be triggered are: | ||
* the change of state of [[measures]] | * the change of state of [[measures]] | ||
* the activation of [[scenarios]] | |||
* the activation of [[ | |||
* the activation of [[Event Bundle|event bundles]] | * the activation of [[Event Bundle|event bundles]] | ||
===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 | 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 [[measure]]s. | ||
==Server events and client events== | ==Server events and client events== | ||
| Line 20: | Line 19: | ||
===Server Events=== | ===Server Events=== | ||
: '' Main article: [[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 | 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=== | ===Client Events=== | ||
| Line 35: | Line 34: | ||
==Adding, removing and editing events== | ==Adding, removing and editing events== | ||
Because events can be added to, and removed from | Because events can be added to, and removed from several types of items 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. | ||
{{:Editing Events}} | {{:Editing Events}} | ||
{{Template:Editor_future_design_nav}} | {{Template:Editor_future_design_nav}} | ||
Latest revision as of 15:14, 23 February 2023
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 editing users. 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
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.
- In the ribbon header, select "Stakeholders".
- In the ribbon bar, select "Event Bundles".
- In the left panel, select "Add".
- In the ribbon header, select "Stakeholders".
- In the ribbon bar, select "Event Bundles".
- In the left panel, select the event bundle you wish to duplicate.
- In the left panel, select "Duplicate".
- In the ribbon header, select "Stakeholders".
- In the ribbon bar, select "Event Bundles".
- In the left panel, select the event bundle you wish to remove.
- In the left panel, select "Remove".
Adding, removing and editing events
Because events can be added to, and removed from several types of items 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.
Future Design