weyne/MOOSE
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE.git synced 2025-08-15 10:47:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

FSM docs

Browse Source
This commit is contained in:
FlightControl 2016-12-23 07:02:29 +01:00
parent 7ad4db84bd
commit 54d0c20d5b
3 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Moose Development/Moose/Core/Fsm.lua
View File

@ -15,7 +15,7 @@
-- * A **State** defines a moment in the process.
-- * An **Event** describes an action, that can be triggered both internally as externally in the FSM. An Event can be triggered Embedded or Delayed over time.
--
-- ![Test Image](.\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia1.jpg)
-- ![Test Image](docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia1.jpg)
--
-- An FSM transitions in **4 moments** when an Event is being handled.
-- Each moment can be catched by handling methods defined by the mission designer,
@ -27,7 +27,7 @@
--
-- ** The OnLeave and OnBefore transition methods may return false to cancel the transition.**
--
-- ![Test Image](.\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia3.jpg)
-- ![Test Image](docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia3.jpg)
--
-- The FSM creates for each Event **two Event trigger methods**.
-- There are two modes how Events can be triggered, which is **embedded** and **delayed**:
@ -35,7 +35,7 @@
-- * The method **FSM:Event()** triggers an Event that will be processed **embedded** or **immediately**.
-- * The method **FSM:__Event( seconds )** triggers an Event that will be processed **delayed** over time, waiting x seconds.
--
-- ![Test Image](.\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia4.jpg)
-- ![Test Image](docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia4.jpg)
--
-- 1.1) Define the FSM Rules
-- -------------------------

1
docs/Documentation/Cargo.html
View File

@ -2411,7 +2411,6 @@ The UNIT carrying the package.</p>
<dl class="function">
<dt>
<em></em>
<a id="#(AI_CARGO_UNIT).CargoCarrier" >
<strong>AI_CARGO_UNIT.CargoCarrier</strong>
</a>

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>
</ul>
<p><img src=".\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia1.jpg" alt="Test Image"/></p>
<p><img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia1.jpg" alt="Test Image"/></p>
<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/>
@ -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> <img src=".\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia3.jpg" alt="Test Image"/></p>
<p> <img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia3.jpg" alt="Test Image"/></p>
<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>
@ -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>
</ul>
<p> <img src=".\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia4.jpg" alt="Test Image"/></p>
<p> <img src="docs\Presentations\DOC.MOOSE - FSM - 1. Concepts\Dia4.jpg" alt="Test Image"/></p>
<h2>1.1) Define the FSM Rules</h2>