Event - Revision history

Frank@tygron.nl at 14:44, 15 July 2026

2026-07-15T14:44:16Z

← Older revision		Revision as of 14:44, 15 July 2026
Line 23:		Line 23:
	===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 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==		==Adding and removing event bundles==

Frank@tygron.nl at 13:30, 8 July 2026

2026-07-08T13:30:12Z

← Older revision		Revision as of 13:30, 8 July 2026
Line 54:		Line 54:

	==Adding, removing and editing 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~~.		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.

	{{:Editing Events}}		{{:Editing Events}}

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

Frank@tygron.nl at 09:03, 8 July 2026

2026-07-08T09:03:01Z

← Older revision		Revision as of 09:03, 8 July 2026
Line 3:		Line 3:
	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.		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 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.		Events are very basic instructions for the {{software}} to execute. For this reason, they can only be predefined by [[Account management#Different account types\|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==		==Where events can be used==
Line 12:		Line 12:

	===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 [[measure]]s.		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 Menu]]s 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 28:		Line 28:
	{{editor location\|Event Bundles}}		{{editor location\|Event Bundles}}
	[[File:bundles-left.jpg\|framed\|left\|The [[Left Panel]] allows you to add, remove, and select event bundles.]]		[[File:bundles-left.jpg\|framed\|left\|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.		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.
	{{Editor steps\|title=add an event bundle\|In the ribbon header, select ~~"Stakeholders"~~.\|In the ribbon bar, select "Event Bundles".\|In the left panel, select "Add".}}		{{Editor steps
	{{Editor steps\|title=duplicate an event bundle\|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".}}		\|title=add an event bundle
	{{Editor steps\|title=remove an event bundle\|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".}}~~<br clear=all>~~		\|In the ribbon header, select [[Future Design]].
			\|In the ribbon bar, select "Event Bundles".
			\|In the left panel, select "Add".
			}}

			{{Editor steps
			\|title=duplicate an event bundle
			\|In the ribbon header, select [[Future Design]].
			\|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".
			}}

			{{Editor steps
			\|title=remove an event bundle
			\|In the ribbon header, select [[Future Design]].
			\|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==		==Adding, removing and editing events==

Frank@tygron.nl: /* Event Bundles */

2023-02-23T15:14:15Z

Event Bundles

← Older revision		Revision as of 15:14, 23 February 2023
Line 12:		Line 12:

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

Frank@tygron.nl: /* Event Bundles */

2023-02-23T15:13:32Z

Event Bundles

← Older revision		Revision as of 15:13, 23 February 2023
Line 12:		Line 12:

	===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~~ [[~~Water Storage (Indicator)\|allowed water level increase~~]] ~~for an area, to rewatch~~ a cinematic~~, or to trigger the sending of a predefined message~~.		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.

	==Server events and client events==		==Server events and client events==

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

2023-01-30T14:16:48Z

Server Events

← Older revision		Revision as of 14:16, 30 January 2023
Line 19:		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 project data 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]] data and the indicator scores; changes which are also visible and possibly important to other stakeholders.

	===Client Events===		===Client Events===

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

2023-01-30T14:16:36Z

Server Events

← Older revision		Revision as of 14:16, 30 January 2023
Line 19:		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 ~~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 data and the indicator scores; changes which are also visible and possibly important to other stakeholders.

	===Client Events===		===Client Events===

Frank@tygron.nl at 16:11, 5 October 2022

2022-10-05T16:11:25Z

← Older revision		Revision as of 16:11, 5 October 2022
Line 1:		Line 1:
	Events in the {{software}} 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 {{software}} can cause events to ~~fire~~. Examples include the planning of a [[measures\|measure]], or ~~the answering of a [[messages]]~~.		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 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.		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 ~~defined~~ by [[User#Editor\|editing users]]. But by using events, it is possible to make a project more complex, and ~~more effective for the participants of a [[project session\|session]]~~.		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==

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

2022-10-05T16:05:52Z

Adding, removing and editing events

← Older revision		Revision as of 16:05, 5 October 2022
Line 34:		Line 34:

	==Adding, removing and editing events==		==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.		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}}

Frank@tygron.nl: /* Where events can be used */

2022-10-05T16:04:32Z

Where events can be used

← Older revision		Revision as of 16:04, 5 October 2022
Line 8:		Line 8:
	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 answering of [[messages]]		* the activation of [[scenarios]]
	* the activation of [[~~levels~~]]
	* the activation of [[Event Bundle\|event bundles]]		* the activation of [[Event Bundle\|event bundles]]