FSM documentation phase 1 done.

2025-10-29 16:58:06 +00:00 · 2017-01-05 08:42:07 +01:00 · 2017-01-05 08:42:07 +01:00 · 640af3d964
commit 640af3d964
parent 3017f10906
61 changed files with 59405 additions and 38 deletions
--- a/Development/Moose/Core/Fsm.lua
+++ b/Development/Moose/Core/Fsm.lua
@ -105,8 +105,9 @@
 -- 
 --        FsmDemo:__Switch( 5, FsmUnit ) -- Trigger the next Switch event to happen in 5 seconds.
 -- 
-- This example is fully implemented in the following MOOSE test mission:
+-- This example is fully implemented in the MOOSE test mission on GITHUB: [FSM-100 - Transition Explanation](https://github.com/FlightControl-Master/MOOSE/blob/master/Moose%20Test%20Missions/FSM%20-%20Finite%20State%20Machine/FSM-100%20-%20Transition%20Explanation/FSM-100%20-%20Transition%20Explanation.lua)
 -- 
+-- ### Some additional comments:
 -- 
 -- Note that transition rules can be declared with a few variations:
 -- 
--- a/Update/l10n/DEFAULT/Moose.lua
+++ b/Update/l10n/DEFAULT/Moose.lua
--- a/Setup/Moose.lua
+++ b/Setup/Moose.lua
--- a/Caucasus/APL-001
+++ b/Caucasus/APL-001
--- a/Nevada/APL-002
+++ b/Nevada/APL-002
--- a/CleanUp/ACL-001
+++ b/CleanUp/ACL-001
--- a/Balancing/AIB-001
+++ b/Balancing/AIB-001
--- a/Balancing/AIB-002
+++ b/Balancing/AIB-002
--- a/Balancing/AIB-003
+++ b/Balancing/AIB-003
--- a/Boarding/CGO-001
+++ b/Boarding/CGO-001
--- a/Unboarding/CGO-002
+++ b/Unboarding/CGO-002
--- a/Transferring/CGO-003
+++ b/Transferring/CGO-003
--- a/Boarding/CGO-101
+++ b/Boarding/CGO-101
--- a/Unboarding/CGO-102
+++ b/Unboarding/CGO-102
--- a/Transferring/CGO-103
+++ b/Transferring/CGO-103
--- a/Boarding/CGO-201
+++ b/Boarding/CGO-201
--- a/Unboarding/CGO-202
+++ b/Unboarding/CGO-202
--- a/Detection/DET-001
+++ b/Detection/DET-001
--- a/Reporting/DET-101
+++ b/Reporting/DET-101
--- a/Helicopters/ESC-001
+++ b/Helicopters/ESC-001
--- a/Explanation/FSM-100
+++ b/Explanation/FSM-100
--- a/Commands/GRP-200
+++ b/Commands/GRP-200
--- a/WayPoints/GRP-300
+++ b/WayPoints/GRP-300
--- a/Commands/Moose_Test_WRAPPER.miz
+++ b/Commands/Moose_Test_WRAPPER.miz
--- a/Options/MEN-001
+++ b/Options/MEN-001
--- a/Coalition/MEN-002
+++ b/Coalition/MEN-002
--- a/Options/MEN-003
+++ b/Options/MEN-003
--- a/Trainer/MIT-001
+++ b/Trainer/MIT-001
--- a/Missions/MOOSE_Test_Template.miz
+++ b/Missions/MOOSE_Test_Template.miz
--- a/Patrolling/PAT-001
+++ b/Patrolling/PAT-001
--- a/Scheduling/SCH-000
+++ b/Scheduling/SCH-000
--- a/Scheduling/SCH-001
+++ b/Scheduling/SCH-001
--- a/Scheduling/SCH-100
+++ b/Scheduling/SCH-100
--- a/Scheduling/SCH-110
+++ b/Scheduling/SCH-110
--- a/Scheduler/SCH-200
+++ b/Scheduler/SCH-200
--- a/Scheduling/SCH-300
+++ b/Scheduling/SCH-300
--- a/Scheduling/SCH-310
+++ b/Scheduling/SCH-310
--- a/Sets/SET-001
+++ b/Sets/SET-001
--- a/Sets/SET-101
+++ b/Sets/SET-101
--- a/Sets/SET-201
+++ b/Sets/SET-201
--- a/Evasion/SEV-001
+++ b/Evasion/SEV-001
--- a/Spawning/SPA-010
+++ b/Spawning/SPA-010
--- a/Spawning/SPA-100
+++ b/Spawning/SPA-100
--- a/Spawning/SPA-110
+++ b/Spawning/SPA-110
--- a/Spawning/SPA-120
+++ b/Spawning/SPA-120
--- a/Spawning/SPA-200
+++ b/Spawning/SPA-200
--- a/Spawning/SPA-220
+++ b/Spawning/SPA-220
--- a/position/SPA-310
+++ b/position/SPA-310
--- a/position/SPA-320
+++ b/position/SPA-320
--- a/position/SPA-330
+++ b/position/SPA-330
--- a/position/SPA-340
+++ b/position/SPA-340
--- a/Dispatching/TAD-010
+++ b/Dispatching/TAD-010
--- a/Modelling/TSK-010
+++ b/Modelling/TSK-010
--- a/Modelling/TSK-020
+++ b/Modelling/TSK-020
--- a/Zones/ZON-100
+++ b/Zones/ZON-100
--- a/Zones/ZON-200
+++ b/Zones/ZON-200
--- a/Zones/ZON-300
+++ b/Zones/ZON-300
--- a/Zones/ZON-400
+++ b/Zones/ZON-400
--- a/Zones/ZON-500
+++ b/Zones/ZON-500
--- a/docs/Documentation/Fsm.html
+++ b/docs/Documentation/Fsm.html
@ -189,8 +189,9 @@ and one additional parameter that was given when the event was triggered, which
 <pre><code>   FsmDemo:__Switch( 5, FsmUnit ) -- Trigger the next Switch event to happen in 5 seconds.
 </code></pre>

-<p>This example is fully implemented in the following MOOSE test mission:</p>
+<p>This example is fully implemented in the MOOSE test mission on GITHUB: <a href="https://github.com/FlightControl-Master/MOOSE/blob/master/Moose%20Test%20Missions/FSM%20-%20Finite%20State%20Machine/FSM-100%20-%20Transition%20Explanation/FSM-100%20-%20Transition%20Explanation.lua">FSM-100 - Transition Explanation</a></p>

+<h3>Some additional comments:</h3>

 <p>Note that transition rules can be declared with a few variations:</p>

--- 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.</p>
 	


+	
+<p> Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.</p>
+
 </dd>
 </dl>
 		<dl class="function">
@ -2166,7 +2169,7 @@ when nothing was spawned.</p>
 		<dl class="function">
 <dt>

-		<em></em>
+		<em>#number</em>
 <a id="#(SPAWN).SpawnMaxGroups" >
 <strong>SPAWN.SpawnMaxGroups</strong>
 </a>
@ -2183,7 +2186,7 @@ when nothing was spawned.</p>
 		<dl class="function">
 <dt>

-		<em></em>
+		<em>#number</em>
 <a id="#(SPAWN).SpawnMaxUnitsAlive" >
 <strong>SPAWN.SpawnMaxUnitsAlive</strong>
 </a>