How to Use Message Popup Rule (Applications)

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The information in this Wiki Page gives practical examples of how to use the Message Popup Rule in Sessions to create messages that will appear after specific events in T:ANE, TRS19, TRS22 and Trainz Plus.

For information of how to configure the Message Popup Rule in Trainz, see the Trainz Wiki Page at:- How to Use Message Popup Rule

Notes: Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The Message Popup Rule is a Trainz Session Rule that creates onscreen messages for users in Driver Mode Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The Close Message Popup Rule is a Trainz Session Rule that closes onscreen messages for users in Driver Mode

Application 1: Timed Message

	The Scenario:
	A Message Popup is activated by a track trigger event and is automatically closed by a timed event

Rules Used:

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Trigger Check Rule to trigger the message event Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Simultaneous List Rule to force all child rules to be executed at the same time Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Message Popup Rule to open a message window on the screen Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Wait Rule to wait a set time interval Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Close Message Popup Rule to close the message window

	Session Editor Screenshot:

Description:

Line  1 : Trigger Check The event is triggered when a consist passes over a track trigger but any event could be used, such as a Navigation Point, a TimeCheck, a Wait On ... or Wait For ..., etc. As long as the following rules are child rules of the trigger event. This executes the following lines:- Line  2 : Simultaneous List This forces all the following child rules to be executed at the same time. Events such as the Trigger Check that execute their child rules in order would not work in this example because everything else would be forced to wait until the Message Popup has been closed. Using the Simultaneous List Rule avoids this problem. Events that execute their child rules simultaneously would not need the Simultaneous List Rule (see next example). This executes the following lines:- Line  3 : Message Popup This places the message window on the screen and waits for it to be closed either manually (by the user) or by another rule Line  4 : Wait This forces a wait for a set time period, in this case 20 seconds but any time interval can be set. At the end of that period the Wait Rule will execute its own set of child rules. This executes the following line:- Line  5 : Close Message Popup The message window is closed

Application 2: Navigation Point/Train Stopped Event

	The Scenario:
	A Message Popup is activated by a navigation event and is automatically closed by a train stopped event

	Preconditions:
	Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Navigation Display Rule to create the navigation point set

Rules Used:

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Navigation Display Rule to create the navigation point set (in Preconditions above) Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Wait on Navigation Point Rule to trigger the message event Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Message Popup Rule to open a message window on the screen Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Wait on Train Stop/Start Rule to trigger an event when the consist stops moving Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Close Message Popup Rule to close the message window

	Session Editor Screenshot:

	Description:
	Line  1 : Wait on Navigation Point The event is triggered when a consist reaches a preset navigation point. This rule executes all its child rules simultaneously so no Simultaneous List Rule is required in this example. This executes the following lines:- Line  2 : Message Popup This places the message window on the screen and waits for it to be closed either manually (by the user) or by another rule Line  3 : Wait on Train Stop/Start When the consist comes to a stop then it will execute its own set of child rules. This executes the following line:- Line  4 : Close Message Popup The message window is closed
	In this example, the Close Message Popups Rule could be replaced by lines 2, 3, 4 and 5 from the Timed Message example shown above to produce a new message when the train stops moving and that message would be closed after a set time interval.

Information of setting and using Navigation Points can be found on the Trainz Wiki Page at:- How to Use Navigation Point Rules

---

---

Trainz Wiki

More Tutorials and Guides to Using Trainz How to Guides Driver Commands List Session Rules List (Alphabetical) with Parameters Session Rules List (Categories) With Parameters

---

This page was created by Trainz user pware in April 2018 and was last updated as shown below.

---