FlightControl-Master/MOOSE
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE.git synced 2025-10-29 16:58:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

FSM

Browse Source
This commit is contained in:
FlightControl 2016-12-23 07:13:20 +01:00
parent d7e3d5fc79
commit aa3a75350a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/Documentation/Fsm.html
View File

@ -89,7 +89,7 @@ It is a fantastic development, this module.</p>
<li>An <strong>Event</strong> describes an action, that can be triggered both internally as externally in the FSM. An Event can be triggered Embedded or Delayed over time.</li> <li>An <strong>Event</strong> describes an action, that can be triggered both internally as externally in the FSM. An Event can be triggered Embedded or Delayed over time.</li>
</ul> </ul>
<p><img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia1.jpg" alt="Test Image"/></p> <p><img src=".\Presentations\FSM\Dia1.jpg" alt="Test Image"/></p>
<p>An FSM transitions in <strong>4 moments</strong> when an Event is being handled. <br/> <p>An FSM transitions in <strong>4 moments</strong> when an Event is being handled. <br/>
Each moment can be catched by handling methods defined by the mission designer, <br/> Each moment can be catched by handling methods defined by the mission designer, <br/>
@ -103,7 +103,7 @@ These methods define the flow of the FSM process; because in those methods the F
<p><em>* The OnLeave and OnBefore transition methods may return false to cancel the transition.</em>*</p> <p><em>* The OnLeave and OnBefore transition methods may return false to cancel the transition.</em>*</p>
<p> <img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia3.jpg" alt="Test Image"/></p> <p> <img src=".\Presentations\FSM\Dia3.jpg" alt="Test Image"/></p>
<p>The FSM creates for each Event <strong>two Event trigger methods</strong>. <br/> <p>The FSM creates for each Event <strong>two Event trigger methods</strong>. <br/>
There are two modes how Events can be triggered, which is <strong>embedded</strong> and <strong>delayed</strong>:</p> There are two modes how Events can be triggered, which is <strong>embedded</strong> and <strong>delayed</strong>:</p>
@ -113,7 +113,7 @@ There are two modes how Events can be triggered, which is <strong>embedded</stro
<li>The method <strong>FSM:__Event( seconds )</strong> triggers an Event that will be processed <strong>delayed</strong> over time, waiting x seconds.</li> <li>The method <strong>FSM:__Event( seconds )</strong> triggers an Event that will be processed <strong>delayed</strong> over time, waiting x seconds.</li>
</ul> </ul>
<p> <img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia4.jpg" alt="Test Image"/></p> <p> <img src=".\Presentations\FSM\Dia4.jpg" alt="Test Image"/></p>
<h2>1.1) Define the FSM Rules</h2> <h2>1.1) Define the FSM Rules</h2>

2
docs/Documentation/Spawn.html
View File

@ -2489,7 +2489,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 )
<p> Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.</p> <p> When the first Spawn executes, all the Groups need to be made visible before start.</p>
</dd> </dd>
</dl> </dl>