From 54d0c20d5b361668b951a68b5065037949f23ef7 Mon Sep 17 00:00:00 2001 From: FlightControl Date: Fri, 23 Dec 2016 07:02:29 +0100 Subject: [PATCH] FSM docs --- Moose Development/Moose/Core/Fsm.lua | 6 +++--- docs/Documentation/Cargo.html | 1 - docs/Documentation/Fsm.html | 6 +++--- 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/Moose Development/Moose/Core/Fsm.lua b/Moose Development/Moose/Core/Fsm.lua index 0b42c1656..586b1deeb 100644 --- a/Moose Development/Moose/Core/Fsm.lua +++ b/Moose Development/Moose/Core/Fsm.lua @@ -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 -- ------------------------- diff --git a/docs/Documentation/Cargo.html b/docs/Documentation/Cargo.html index 0319727b8..c03fa6ee7 100644 --- a/docs/Documentation/Cargo.html +++ b/docs/Documentation/Cargo.html @@ -2411,7 +2411,6 @@ The UNIT carrying the package.

- AI_CARGO_UNIT.CargoCarrier diff --git a/docs/Documentation/Fsm.html b/docs/Documentation/Fsm.html index aa5a23926..569d760c2 100644 --- a/docs/Documentation/Fsm.html +++ b/docs/Documentation/Fsm.html @@ -89,7 +89,7 @@ It is a fantastic development, this module.

  • 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

    +

    Test Image

    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,
    @@ -103,7 +103,7 @@ These methods define the flow of the FSM process; because in those methods the F

    * The OnLeave and OnBefore transition methods may return false to cancel the transition.*

    -

    Test Image

    +

    Test Image

    The FSM creates for each Event two Event trigger methods.
    There are two modes how Events can be triggered, which is embedded and delayed:

    @@ -113,7 +113,7 @@ There are two modes how Events can be triggered, which is embeddedThe method FSM:__Event( seconds ) triggers an Event that will be processed delayed over time, waiting x seconds. -

    Test Image

    +

    Test Image

    1.1) Define the FSM Rules