Event Bundle: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:Api_future_design.png|thumb|right|400px|[[Event Bundle]]s in relation to other [[Action]]s]] | [[File:Api_future_design.png|thumb|right|400px|[[Event Bundle]]s in relation to other [[Action]]s]] | ||
Event | Event Bundles are collections of [[Coded Event]]s 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 are [[Action]]s that can be added to [[Action Menu]]s. A Stakeholder can apply an Event Bundle, triggering both Client and Server Events directly. This can be useful to, for example, restart a cinematic. | ||
Coded Events in Event Bundles can be split into two groups: Server Events and Client Events. | |||
Events in | |||
===Server Events=== | ===Server Events=== | ||
| Line 9: | Line 8: | ||
===Client Events=== | ===Client Events=== | ||
[[Client Event]]s are not communicated to the server 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. | [[Client Event]]s are not communicated to the server 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, starting a [[Cinematic]] or the visualization of a [[weather]] effect. | ||
{{article end | {{article end | ||
| Line 18: | Line 17: | ||
* [[Client Event]]s | * [[Client Event]]s | ||
* [[Server Event]]s | * [[Server Event]]s | ||
* [[Coded Event]] | |||
* [[Action Menu]] | |||
* [[Cinematic]] | * [[Cinematic]] | ||
* [[ | * [[Action]] | ||
|api=*[[Api session items eventbundles]] | |api=*[[Api session items eventbundles]] | ||
Latest revision as of 12:27, 13 November 2026
Event Bundles are collections of Coded 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 are Actions that can be added to Action Menus. A Stakeholder can apply an Event Bundle, triggering both Client and Server Events directly. This can be useful to, for example, restart a cinematic.
Coded Events in Event Bundles can be split into two groups: Server Events and Client Events.
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 spatially, visually in the 3D Visualization, and the indicator scores; changes which are also visible and possibly important to other stakeholders.
Client Events
Client Events are not communicated to the server 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, starting a Cinematic or the visualization of a weather effect.
How-to's
See also
API Endpoints
Future Design
- Test Run • Actions • Action Menus • Measures • Parametric • Attributes • Levee Types • Upgrade Types • Event Bundles • Active Stakeholders
- Actions
- Building • TerrainSpatial • GridSpatial • TiffSpatial • LeveeSpatial • UpgradeSpatial
- Special Option