Client Event - Revision history

Maxim@tygron.com: /* List of Client Event types */

2026-07-07T11:02:48Z

List of Client Event types

← Older revision		Revision as of 11:02, 7 July 2026
Line 41:		Line 41:
	\|-		\|-
	\|'''RANDOM_ACTIVATE_POPUP_PERCENTAGE'''		\|'''RANDOM_ACTIVATE_POPUP_PERCENTAGE'''
	\|''~~...~~''		\|''Respond to a popup with a given change with the first answer of that popup''
	\|-		\|-
	\|'''SELECT_HOTSPOT'''		\|'''SELECT_HOTSPOT'''

Maxim@tygron.com: /* List of Client Event types */

2026-07-07T11:02:24Z

List of Client Event types

← Older revision		Revision as of 11:02, 7 July 2026
Line 39:		Line 39:
	\|'''FORCE_ACTIVATE_VIDEO'''		\|'''FORCE_ACTIVATE_VIDEO'''
	\|''Force a selected video to play on the client system''		\|''Force a selected video to play on the client system''
	\|-
	~~\|'''GOTO_START_LOCATION'''~~
	~~\|''Sets the user's viewpoint to a predefined starting position''~~
	\|-
	~~\|'''MESSAGE_ANSWERED'''~~
	~~\|''Sends a standard reply to a message, based on the selected Answer [[ID]]''~~
	\|-
	~~\|'''MESSAGE_MOTIVATION_ANSWER'''~~
	~~\|''Sends a reply to a message, with a predefined motivation text added''~~
	\|-		\|-
	\|'''RANDOM_ACTIVATE_POPUP_PERCENTAGE'''		\|'''RANDOM_ACTIVATE_POPUP_PERCENTAGE'''
Line 71:		Line 62:
	\|-		\|-
	\|'''TILE_ATTENTION'''		\|'''TILE_ATTENTION'''
	\|''~~...~~''		\|''Gives visual attention for a given point and amount of seconds''
	\|}		\|}

Maxim@tygron.com at 15:13, 6 July 2026

2026-07-06T15:13:13Z

← Older revision		Revision as of 15:13, 6 July 2026
Line 1:		Line 1:
	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 the flashing of an [[Actions\|action]] menu or an [[Indicators\|indicator]] to draw the user's attention, or the visualization of a [[Weather\|weather]] effect, such as a rain storm.		Client events are not communicated to the {{software server}} and are usually a graphical effect for the [[stakeholder]] who triggered the event. Examples of this include the flashing of an [[Actions\|action]] menu or an [[Indicators\|indicator]] to draw the user's attention, or the visualization of a [[Weather\|weather]] effect, such as a rain storm.

	==How do Client Events relate to the {{software}}==		==How do Client Events relate to the {{software}}==

Maxim@tygron.com at 15:12, 6 July 2026

2026-07-06T15:12:12Z

← Older revision		Revision as of 15:12, 6 July 2026
Line 81:		Line 81:
	As mentioned above, events can be added to a project element on multiple occasions and locations. Please refer to the main articles relating to these elements for more information about the specific steps to take.		As mentioned above, events can be added to a project element on multiple occasions and locations. Please refer to the main articles relating to these elements for more information about the specific steps to take.

	Generally, select the element (e.g., measures, levels) in the [[Left Panel\|left panel]], then add events via the [[Right Panel\|right panel]]. Click the 'Add Event' button at the bottom of the right panel to create a default 'NO_DEF' event. Selecting an Event on the list and using the 'Remove Event' button deletes the event from the list.		Generally, select the element (e.g., measures, levels) in the [[Left Panel\|left panel]], then add events via the [[Right Panel\|right panel]]. Click the '''Add Event''' button at the bottom of the right panel to create a default '''NO_DEF''' event. Selecting an Event on the list and using the 'Remove Event' button deletes the event from the list.

	Selecting an event ~~on the right panel also~~ opens up the [[Bottom Panel\|bottom panel]] ~~where~~ the ~~actual~~ event type ~~can be selected~~. ~~This selection can then be confirmed on the bottom panel by using the~~ 'Commit' ~~button. The~~ 'Cancel' ~~button clears the selection on the bottom panel~~.		Selecting an event opens the [[Bottom Panel\|bottom panel]] to choose the event type. Confirm with '''Commit''' or clear with '''Cancel'''.

	{{Editor steps\|title=add events to a project element\|Select Project Element to have events added to\|Select the Event option on the left panel\|Select 'Add event' on the bottom of the right panel\|Select the newly added event on the right panel\|Select the desired client event from the bottom panel\|Confirm the selection with the 'Commit' button (or use the 'Cancel' button to clear the selection}}		{{Editor steps\|title=add events to a project element\|Select Project Element to have events added to\|Select the Event option on the left panel\|Select 'Add event' on the bottom of the right panel\|Select the newly added event on the right panel\|Select the desired client event from the bottom panel\|Confirm the selection with the 'Commit' button (or use the 'Cancel' button to clear the selection}}

Maxim@tygron.com at 15:10, 6 July 2026

2026-07-06T15:10:51Z

← Older revision		Revision as of 15:10, 6 July 2026
Line 81:		Line 81:
	As mentioned above, events can be added to a project element on multiple occasions and locations. Please refer to the main articles relating to these elements for more information about the specific steps to take.		As mentioned above, events can be added to a project element on multiple occasions and locations. Please refer to the main articles relating to these elements for more information about the specific steps to take.

	~~In general~~, ~~adding Events to an element in the {{software}} happens on the [[Right Panel\|right panel]], after selecting~~ the element (ex. measures, levels~~, etc~~) ~~to have an event added to on~~ the [[Left Panel\|left panel]] ~~first. Select on~~ the right panel ~~bottom~~ the 'Add Event' button; a default ~~blank event named '~~'NO_DEF'~~' is created in the list above the buttons~~. Selecting an Event on the list and using the 'Remove Event' button deletes the event from the list.		Generally, select the element (e.g., measures, levels) in the [[Left Panel\|left panel]], then add events via the [[Right Panel\|right panel]]. Click the 'Add Event' button at the bottom of the right panel to create a default 'NO_DEF' event. Selecting an Event on the list and using the 'Remove Event' button deletes the event from the list.

	Selecting an event on the right panel also opens up the [[Bottom Panel\|bottom panel]] where the actual event type can be selected. This selection can then be confirmed on the bottom panel by using the 'Commit' button. The 'Cancel' button clears the selection on the bottom panel.		Selecting an event on the right panel also opens up the [[Bottom Panel\|bottom panel]] where the actual event type can be selected. This selection can then be confirmed on the bottom panel by using the 'Commit' button. The 'Cancel' button clears the selection on the bottom panel.

Frank@tygron.nl at 12:14, 2 July 2026

2026-07-02T12:14:20Z

← Older revision		Revision as of 12:14, 2 July 2026
Line 41:		Line 41:
	\|-		\|-
	\|'''GOTO_START_LOCATION'''		\|'''GOTO_START_LOCATION'''
	\|''Sets the user's ~~view point~~ to a predefined starting position''		\|''Sets the user's viewpoint to a predefined starting position''
	\|-		\|-
	\|'''MESSAGE_ANSWERED'''		\|'''MESSAGE_ANSWERED'''
Line 89:		Line 89:
	<br clear=both>		<br clear=both>
	==Changing the properties of a Client Event in a project==		==Changing the properties of a Client Event in a project==
	The properties of events can be edited on the bottom panel (see image above). On this panel a linked [[ID]] of a measure or cinematic can be linked to an event for instance. Any ~~changed~~ made need to be confirmed first with the 'Commit' button, or ~~cancelled~~ with the 'Cancel' button.		The properties of events can be edited on the bottom panel (see image above). On this panel a linked [[ID]] of a measure or cinematic can be linked to an event for instance. Any changes made need to be confirmed first with the 'Commit' button, or canceled with the 'Cancel' button.

Frank@tygron.nl at 12:12, 2 July 2026

2026-07-02T12:12:30Z

← Older revision		Revision as of 12:12, 2 July 2026
Line 1:		Line 1:
	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 the flashing of an [[Actions\|action]] menu or an [[Indicators\|indicator]] to draw the user's attention, or the visualization of a [[Weather\|weather]] effect, such as a rain storm.		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 the flashing of an [[Actions\|action]] menu or an [[Indicators\|indicator]] to draw the user's attention, or the visualization of a [[Weather\|weather]] effect, such as a rain storm.

	==How do Client Events relate to the {{software}}==		==How do Client Events relate to the {{software}}==

Frank@tygron.nl at 12:11, 2 July 2026

2026-07-02T12:11:29Z

← Older revision		Revision as of 12:11, 2 July 2026
Line 85:		Line 85:
	Selecting an event on the right panel also opens up the [[Bottom Panel\|bottom panel]] where the actual event type can be selected. This selection can then be confirmed on the bottom panel by using the 'Commit' button. The 'Cancel' button clears the selection on the bottom panel.		Selecting an event on the right panel also opens up the [[Bottom Panel\|bottom panel]] where the actual event type can be selected. This selection can then be confirmed on the bottom panel by using the 'Commit' button. The 'Cancel' button clears the selection on the bottom panel.

	{{Editor steps\|title=add events to a project element\|Select Project Element to have events added to\|Select the Event option on the left panel\|Select 'Add event' on the bottom of the right panel\|Select the newly added event on the right panel\|Select the desired ~~server~~ event from the bottom panel\|Confirm the selection with the 'Commit' button (or use the 'Cancel' button to clear the selection}}		{{Editor steps\|title=add events to a project element\|Select Project Element to have events added to\|Select the Event option on the left panel\|Select 'Add event' on the bottom of the right panel\|Select the newly added event on the right panel\|Select the desired client event from the bottom panel\|Confirm the selection with the 'Commit' button (or use the 'Cancel' button to clear the selection}}
	[[File:ClientEventBottomPanel-Q3-2015.jpg\|frame\|left\|Event bundle [[Bottom Panel\|bottom panel]] with 'Commit' and 'Cancel' buttons]]		[[File:ClientEventBottomPanel-Q3-2015.jpg\|frame\|left\|Event bundle [[Bottom Panel\|bottom panel]] with 'Commit' and 'Cancel' buttons]]
	<br clear=both>		<br clear=both>
	==Changing the properties of a Client Event in a project==		==Changing the properties of a Client Event in a project==
	The properties of events can be edited on the bottom panel (see image above). On this panel a linked [[ID]] of a measure or cinematic can be linked to an event for instance. Any changed made need to be confirmed first with the 'Commit' button, or cancelled with the 'Cancel' button.		The properties of events can be edited on the bottom panel (see image above). On this panel a linked [[ID]] of a measure or cinematic can be linked to an event for instance. Any changed made need to be confirmed first with the 'Commit' button, or cancelled with the 'Cancel' button.

Frank@tygron.nl: /* How do Client Events relate to the {{software}} */

2026-07-02T12:10:57Z

How do Client Events relate to the {{software}}

← Older revision		Revision as of 12:10, 2 July 2026
Line 2:		Line 2:

	==How do Client Events relate to the {{software}}==		==How do Client Events relate to the {{software}}==
	Client Events can be used on multiple locations in the {{software}}; as part of a [[Measures\|measure]], as part of a larger [[Event Bundle]]s in ~~the~~ [[Action Menu]], or during a [[Cinematics\|cinematic sequence]]. Client Events do not communicate with the server, but trigger a reaction locally on the user's system.		Client Events can be used on multiple locations in the {{software}}; as part of a [[Measures\|measure]], as part of a larger [[Event Bundle]]s in an [[Action Menu]], or during a [[Cinematics\|cinematic sequence]]. Client Events do not communicate with the server, but trigger a reaction locally on the user's system.
	:''See also: [[Measures]], [[Actions]] & [[Cinematics]]''		:''See also: [[Measures]], [[Actions]] & [[Cinematics]]''

Frank@tygron.nl at 12:10, 2 July 2026

2026-07-02T12:10:44Z

← Older revision		Revision as of 12:10, 2 July 2026
Line 2:		Line 2:

	==How do Client Events relate to the {{software}}==		==How do Client Events relate to the {{software}}==
	Client Events can be used on multiple locations in the {{software}}; as part of a [[Measures\|measure]], as part of a larger [[~~Events#~~Event ~~Bundles\|event bundle~~]] in the [[~~Actions\|action~~]] ~~menu~~, or during a [[Cinematics\|cinematic sequence]]. Client Events do not communicate with the server, but trigger a reaction locally on the user's system.		Client Events can be used on multiple locations in the {{software}}; as part of a [[Measures\|measure]], as part of a larger [[Event Bundle]]s in the [[Action Menu]], or during a [[Cinematics\|cinematic sequence]]. Client Events do not communicate with the server, but trigger a reaction locally on the user's system.
	:''See also: [[Measures]], [[Actions]] & [[Cinematics]]''		:''See also: [[Measures]], [[Actions]] & [[Cinematics]]''