MOOSE generated documentation [skip ci]

This commit is contained in:
Applevangelist
2022-10-29 08:17:27 +00:00
parent 0f55b75634
commit c2cbd9d497
77 changed files with 1913 additions and 1872 deletions

View File

@@ -1656,7 +1656,7 @@ Controls a network of short range air/missile defense groups.</p>
<p><img src="..\Presentations\TASK_A2A_DISPATCHER\Dia3.JPG" alt="Banner Image"/></p>
<p>The EWR will detect units, will group them, and will dispatch <a href="Task.html">Task</a>s to groups. Depending on the type of target detected, different tasks will be dispatched.
<p>The EWR will detect units, will group them, and will dispatch <a href="Tasking.Task.html">Tasking.Task</a>s to groups. Depending on the type of target detected, different tasks will be dispatched.
Find a summary below describing for which situation a task type is created:</p>
<p><img src="..\Presentations\TASK_A2A_DISPATCHER\Dia9.JPG" alt="Banner Image"/></p>
@@ -1768,7 +1768,7 @@ If too large, any airborne cap may not be able to reach the detected target area
<h2>4. Set <strong>Scoring</strong> and <strong>Messages</strong>:</h2>
<p>The TASK_A2A_DISPATCHER is a state machine. It triggers the event Assign when a new player joins a <a href="Task.html">Task</a> dispatched by the TASK_A2A_DISPATCHER.
<p>The TASK_A2A_DISPATCHER is a state machine. It triggers the event Assign when a new player joins a <a href="Tasking.Task.html">Tasking.Task</a> dispatched by the TASK_A2A_DISPATCHER.
An <em>event handler</em> can be defined to catch the <strong>Assign</strong> event, and add <strong>additional processing</strong> to set <em>scoring</em> and to <em>define messages</em>,
when the player reaches certain achievements in the task.</p>
@@ -2106,7 +2106,7 @@ So, this method will be called only <strong>ONCE</strong> when a player joins a
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(TASK_A2A_DISPATCHER).AddProcess">TASK_A2A_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Set the default <a href="Process.html">Process</a> template with key ProcessName providing the ProcessClass and the process object when it is assigned to a <a href="Wrapper.Controllable.html">Wrapper.Controllable</a> by the task.</p>
<p>Set the default <a href="##(FSM_PROCESS)">#FSM_PROCESS</a> template with key ProcessName providing the ProcessClass and the process object when it is assigned to a <a href="Wrapper.Controllable.html">Wrapper.Controllable</a> by the task.</p>
</td>
</tr>
<tr class="w3-border">
@@ -4897,7 +4897,7 @@ If too large, any airborne cap may not be able to reach the detected target area
<h2><a id="#(TASK_A2A_DISPATCHER).AddProcess" ><strong>TASK_A2A_DISPATCHER:AddProcess(From, Event, Process, ReturnEvents)</strong></a></h2>
</div>
<p>Set the default <a href="Process.html">Process</a> template with key ProcessName providing the ProcessClass and the process object when it is assigned to a <a href="Wrapper.Controllable.html">Wrapper.Controllable</a> by the task.</p>
<p>Set the default <a href="##(FSM_PROCESS)">#FSM_PROCESS</a> template with key ProcessName providing the ProcessClass and the process object when it is assigned to a <a href="Wrapper.Controllable.html">Wrapper.Controllable</a> by the task.</p>
<div id= "#Functions##AddProcess" class="w3-show w3-white">
<div class="w3-container w3-white" id="functiontype">