Event Bundle - Revision history

Frank@tygron.nl at 14:43, 20 April 2026

2026-04-20T14:43:02Z

← Older revision		Revision as of 14:43, 20 April 2026
Line 18:		Line 18:
	* [[Client Event]]s		* [[Client Event]]s
	* [[Server Event]]s		* [[Server Event]]s

			\|api=*[[Api session items eventbundles]]
	}}		}}
	{{Template:Editor_future_design_nav}}		{{Template:Editor_future_design_nav}}

	[[Category:Items]]		[[Category:Items]]

Frank@tygron.nl: /* Client Events */

2023-02-21T11:03:21Z

Client Events

← Older revision		Revision as of 11:03, 21 February 2023
Line 9:		Line 9:

	===Client Events===		===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.		[[Client Event]]s 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.

	{{article end		{{article end

Frank@tygron.nl: /* Server Events */

2023-02-21T11:03:14Z

Server Events

← Older revision		Revision as of 11:03, 21 February 2023
Line 6:		Line 6:

	===Server 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.		[[Server Event]]s 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===

Frank@tygron.nl: /* How-to */

2023-02-21T11:03:01Z

How-to

← Older revision		Revision as of 11:03, 21 February 2023
Line 11:		Line 11:
	[[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.		[[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.

	~~===How-to==~~=		{{article end
			\|howtos=
	* [[How to add and remove Event Bundles]]		* [[How to add and remove Event Bundles]]
	* [[How to edit Event Bundle events]]		* [[How to edit Event Bundle events]]
			\|seealso=
			* [[Client Event]]s
			* [[Server Event]]s
			}}
	{{Template:Editor_future_design_nav}}		{{Template:Editor_future_design_nav}}

	[[Category:Items]]		[[Category:Items]]

Frank@tygron.nl: /* Client Events */

2023-02-21T11:02:29Z

Client Events

← Older revision		Revision as of 11:02, 21 February 2023
Line 9:		Line 9:

	===Client Events===		===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.
	~~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.

	===How-to===		===How-to===

Frank@tygron.nl: /* Server Events */

2023-02-21T11:02:20Z

Server Events

← Older revision		Revision as of 11:02, 21 February 2023
Line 6:		Line 6:

	===Server 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]] spatially, visually in the [[3D Visualization]], and the indicator scores; changes which are also visible and possibly important to other stakeholders.
	~~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===

Frank@tygron.nl at 11:02, 21 February 2023

2023-02-21T11:02:00Z

← Older revision		Revision as of 11:02, 21 February 2023
Line 1:		Line 1:
			[[File:Api_future_design.png\|thumb\|right\|400px\|[[Event Bundle]]s in relation to other [[Action]]s]]
	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 be added to [[Action Menu]]s, such that stakeholders can trigger these events directly as an action. This can be useful to, for example, rewatch a cinematic.		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 be added to [[Action Menu]]s, such that stakeholders can trigger these events directly as an action. This can be useful to, for example, rewatch a cinematic.

Frank@tygron.nl at 09:31, 21 February 2023

2023-02-21T09:31:23Z

← Older revision		Revision as of 09:31, 21 February 2023
Line 1:		Line 1:
	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 be added to [[~~action menu~~]]s, such that stakeholders can trigger these events directly as an action. This can be useful to, for example, rewatch a cinematic.		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 be added to [[Action Menu]]s, such that stakeholders can trigger these events directly as an action. This can be useful to, for example, rewatch a cinematic.

	==Server events and client events==		==Server events and client events==
Line 10:		Line 10:
	===Client Events===		===Client Events===
	: '' Main article: [[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.		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.

	===How-to===		===How-to===

Frank@tygron.nl at 17:15, 30 January 2023

2023-01-30T17:15:30Z

← Older revision		Revision as of 17:15, 30 January 2023
Line 6:		Line 6:
	===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 3D ~~world~~ and the indicator scores; changes which are also visible and possibly important to other stakeholders.		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===

Frank@tygron.nl: /* Adding, removing and editing events */

2022-10-06T11:17:34Z

Adding, removing and editing events

← Older revision		Revision as of 11:17, 6 October 2022
Line 15:		Line 15:
	* [[How to add and remove Event Bundles]]		* [[How to add and remove Event Bundles]]
	* [[How to edit Event Bundle events]]		* [[How to edit Event Bundle events]]

	~~==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.

	~~{{:Editing Events}}~~

	{{Template:Editor_future_design_nav}}		{{Template:Editor_future_design_nav}}

	[[Category:Items]]		[[Category:Items]]