diff --git a/Moose Development/Moose/Core/Fsm.lua b/Moose Development/Moose/Core/Fsm.lua index 791e32972..49fe28893 100644 --- a/Moose Development/Moose/Core/Fsm.lua +++ b/Moose Development/Moose/Core/Fsm.lua @@ -87,7 +87,7 @@ -- -- ### 1.1.2) Transition Handling -- --- ![Transition Handlers](..\Presentations\FSM\Dia4.jpg) +-- ![Transition Handlers](..\Presentations\FSM\Dia4.JPG) -- -- An FSM transitions in **4 moments** when an Event is being triggered and processed. -- The mission designer can define for each moment specific logic within methods implementations following a defined API syntax. @@ -109,7 +109,7 @@ -- -- ### 1.1.3) Event Triggers -- --- ![Event Triggers](..\Presentations\FSM\Dia5.jpg) +-- ![Event Triggers](..\Presentations\FSM\Dia5.JPG) -- -- The FSM creates for each Event two **Event Trigger methods**. -- There are two modes how Events can be triggered, which is **synchronous** and **asynchronous**: @@ -152,7 +152,7 @@ -- Two Transition Rules are created, where upon the event Switch, -- the FsmDemo will transition from state Green to Red and vise versa. -- --- ![Transition Example](..\Presentations\FSM\Dia6.jpg) +-- ![Transition Example](..\Presentations\FSM\Dia6.JPG) -- -- local FsmDemo = FSM:New() -- #FsmDemo -- FsmDemo:SetStartState( "Green" ) @@ -162,7 +162,7 @@ -- In the above example, the FsmDemo could flare every 5 seconds a Green or a Red flare into the air. -- The next code implements this through the event handling method **OnAfterSwitch**. -- --- ![Transition Flow](..\Presentations\FSM\Dia7.jpg) +-- ![Transition Flow](..\Presentations\FSM\Dia7.JPG) -- -- function FsmDemo:OnAfterSwitch( From, Event, To, FsmUnit ) -- self:E( { From, Event, To, FsmUnit } ) diff --git a/docs/Documentation/Cargo.html b/docs/Documentation/Cargo.html index c03fa6ee7..0319727b8 100644 --- a/docs/Documentation/Cargo.html +++ b/docs/Documentation/Cargo.html @@ -2411,6 +2411,7 @@ The UNIT carrying the package.

+ AI_CARGO_UNIT.CargoCarrier diff --git a/docs/Documentation/Fsm.html b/docs/Documentation/Fsm.html index 0b82c9229..c1be84c0e 100644 --- a/docs/Documentation/Fsm.html +++ b/docs/Documentation/Fsm.html @@ -163,7 +163,7 @@ These rules define when an FSM can transition from a specific state towards an o

1.1.2) Transition Handling

-

Transition Handlers

+

Transition Handlers

An FSM transitions in 4 moments when an Event is being triggered and processed.
The mission designer can define for each moment specific logic within methods implementations following a defined API syntax.
@@ -189,7 +189,7 @@ These parameters are on the correct order: From, Event, To:

1.1.3) Event Triggers

-

Event Triggers

+

Event Triggers

The FSM creates for each Event two Event Trigger methods.
There are two modes how Events can be triggered, which is synchronous and asynchronous:

@@ -237,7 +237,7 @@ It will set the start state of FsmDemo to Green. Two Transition Rules are created, where upon the event Switch, the FsmDemo will transition from state Green to Red and vise versa.

-

Transition Example

+

Transition Example

 local FsmDemo = FSM:New() -- #FsmDemo
  FsmDemo:SetStartState( "Green" )
@@ -248,7 +248,7 @@ the FsmDemo will transition from state Green to Red and vise versa.

 
In the above example, the FsmDemo could flare every 5 seconds a Green or a Red flare into the air.
 The next code implements this through the event handling method OnAfterSwitch.

 
-
Transition Flow

+
Transition Flow

 
 
 function FsmDemo:OnAfterSwitch( From, Event, To, FsmUnit )
    self:E( { From, Event, To, FsmUnit } )
diff --git a/docs/Documentation/Spawn.html b/docs/Documentation/Spawn.html
index 0cd7b6d64..1116db12a 100644
--- a/docs/Documentation/Spawn.html
+++ b/docs/Documentation/Spawn.html
@@ -1692,6 +1692,9 @@ The group that was spawned. You can use this group for further actions.

 	
 
 
+	
+
 Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.

+
@@ -2486,7 +2489,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 ) -

When the first Spawn executes, all the Groups need to be made visible before start.

+

Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.

diff --git a/docs/Presentations/FSM/Dia1.jpg b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia1.JPG similarity index 100% rename from docs/Presentations/FSM/Dia1.jpg rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia1.JPG diff --git a/docs/Presentations/FSM/Dia2.jpg b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia2.JPG similarity index 100% rename from docs/Presentations/FSM/Dia2.jpg rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia2.JPG diff --git a/docs/Presentations/FSM/Dia3.jpg b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia3.JPG similarity index 100% rename from docs/Presentations/FSM/Dia3.jpg rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia3.JPG diff --git a/docs/Presentations/FSM/Dia4.jpg b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia4.JPG similarity index 100% rename from docs/Presentations/FSM/Dia4.jpg rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia4.JPG diff --git a/docs/Presentations/FSM/Dia5.JPG b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia5.JPG similarity index 100% rename from docs/Presentations/FSM/Dia5.JPG rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia5.JPG diff --git a/docs/Presentations/FSM/Dia6.JPG b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia6.JPG similarity index 100% rename from docs/Presentations/FSM/Dia6.JPG rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia6.JPG diff --git a/docs/Presentations/FSM/Dia7.JPG b/docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia7.JPG similarity index 100% rename from docs/Presentations/FSM/Dia7.JPG rename to docs/Presentations/FSM/DOC.MOOSE - FSM - 1. Concepts/Dia7.JPG