How to Use Message Popup Rule (Applications)

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
(Related Session Creation Tutorials:)
m (Trainz Creation Tutorials:)
Line 64: Line 64:
 
'''Related Session Creation Tutorials:'''
 
'''Related Session Creation Tutorials:'''
 
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
 
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
 +
*'''[[Creating a HTML Asset]]'''
 
*'''[[Controlling Junctions in Sessions]]'''
 
*'''[[Controlling Junctions in Sessions]]'''
 
*'''[[Controlling Signals in Sessions]]'''
 
*'''[[Controlling Signals in Sessions]]'''

Revision as of 16:42, 27 May 2018

  • The Message Popup Rule is a T:ANE Session Rule that creates onscreen messages for users in Driver Mode.

This page gives practical examples of how these rules can be used in a session to create messages that appear after an event and automatically close after another event.

Application 1: Timed Message

1. The Scenario:

A Message Popup is activated by a track trigger event and is automatically closed by a timed event.

2. Rules Used:

3. Session Rules Screenshot:

Message Popup.jpg

4. Example Explanation:

  • 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.
    • 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).
      • 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.
        • Line 5: Close Message Popup The message window is closed.

Application 2: Navigation Point and Train Stopped Event Message

1. The Scenario:

A Message Popup is activated by a navigation event and is automatically closed by a train stopped event.

2. Rules Used:

3. Preconditions:

4. Session Rules Screenshot:

Message Popup2.JPG

5. Example Explanation:

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

Trainz Creation Tutorials:

Related Session Creation Tutorials:

Personal tools