fc100716e0
FSM Updates
2017-01-06 11:08:42 +01:00
a5298a950f
Deleting JPG Files ...
2017-01-06 07:42:08 +01:00
743609310b
FSM Documentation
2017-01-06 07:37:20 +01:00
df0adff9f1
FSM Documentation
2017-01-05 22:12:09 +01:00
64092dbb2e
FSM documentation
2017-01-05 16:12:07 +01:00
640af3d964
FSM documentation phase 1 done.
2017-01-05 08:42:07 +01:00
3017f10906
FSM Documentation
2017-01-05 08:34:15 +01:00
56a78f1f28
Added DCS-API submodule
2017-01-04 14:36:00 +01:00
f79539965f
FSM documentation
2017-01-04 11:13:49 +01:00
6bd4442d84
FSM Documentation
2017-01-04 10:40:58 +01:00
335ef0d471
FSM Documentation
2017-01-04 10:33:11 +01:00
d7e3d5fc79
FSM doc
2016-12-23 07:11:22 +01:00
54d0c20d5b
FSM docs
2016-12-23 07:02:29 +01:00
13854370e4
Documentation FSM
2016-12-23 06:50:24 +01:00
2f7dd91259
Added DCS-API submodule
2016-12-22 12:42:24 +01:00
6601f2217a
Removed DCS luadoc, will be re-added as a submodule
2016-12-22 12:41:45 +01:00
cff0d8bb2b
FSM Documentation
2016-12-21 17:31:24 +01:00
cb993c4df5
Switched for Event and State Transition handlers the parameter order
...
The parameters are now: From, Event, To
The old parameter order was: Event, From, To
2016-12-20 09:24:19 +01:00
dc3ce7226e
Documentation
2016-12-19 21:42:17 +01:00
b21f1144fb
Documentation of the BASE class
2016-12-19 21:15:10 +01:00
0f8ed48183
Fixed DETECTION_DISPATCHER (I think)..
...
-- Need to test this in a group.
-- Revised messages adding @ signs, which represent to who the message
is targetted.
2016-12-18 11:39:16 +01:00
ce0be4dcf7
Fixing TASK_DISPATCHER and optimizing reports
2016-12-18 06:09:27 +01:00
23a039b58f
Publish new release
2016-12-16 17:06:43 +01:00
e98d36e314
Fixed all files now
2016-12-16 16:33:58 +01:00
33f42351e4
Progress
2016-12-16 12:56:36 +01:00
995e21e200
Progress
2016-12-16 12:07:11 +01:00
d62acf421e
Progress
2016-12-15 14:51:08 +01:00
9e6fc16cce
Test MP
2016-12-15 10:30:54 +01:00
80f7269651
MP bugfix
2016-12-15 10:14:53 +01:00
b65bdad54f
Updated Menu Triggering
2016-12-15 10:07:07 +01:00
51d8e2b7d8
Progress
2016-12-15 09:50:21 +01:00
63e46ad029
Task documentation and event handler prototypes
2016-12-15 06:57:06 +01:00
7f7570429a
Abort working now as it should... fiew... what a work was that ...
2016-12-14 20:05:45 +01:00
c966929933
Progress
2016-12-14 15:09:10 +01:00
365034ad69
Finalized the SCHEDULER and SCHEDULERDISPATCHER
...
- Done, time to remerge the work.
2016-12-14 11:10:00 +01:00
84e2361829
Progress
2016-12-14 06:59:43 +01:00
761053c95e
Progress
2016-12-14 06:58:24 +01:00
02d4bbf3ff
Getting somewhere, with the new schedulers, the TASK logic works now much better!
...
- Schedulers are stopped when the parent object is destroyed.
- Parent objects are garbage cleaned.
- Destructors are called.
Jippie! Results!!!
2016-12-13 13:05:21 +01:00
e98814e8d4
Progress
...
Fixed that schedulers, which are not attached to an object, after
garbage collect were removed also from the scheduler dispatcher. The
scheduler dispatcher now attaches the schedulers to 2 different tables.
- A weak table ObjectSchedulers, which contains scheduler attached to
objects. When the object is removed, the scheduler is removed also.
- A weak table with PersistentSchedulers, which contains schedulers not
attached to objects. These schedulers are persistent, even after garbage
collection.
I hope this now makes the circle round...
2016-12-13 12:29:28 +01:00
152c8a986d
Pogress
...
- Still a problem, getting obscolete calls after a garbage collect where
i should not get them ...
2016-12-13 12:10:12 +01:00
6c6b26e33e
Progress
2016-12-13 11:25:39 +01:00
e5b386b9e5
Progress
2016-12-13 10:24:19 +01:00
15134d7f4e
Formidastic, now when nillifying the Test1 and Test 3, the destructor of the SCHEDULER is called
...
The references of nillified and garbage collected SCHEDULERS are removed
from the _TIMERDISPATCHER. This results now in schedules that are still
pending to be executed, but are nillified, that these schedules will
never be executed!!!
Sven
2016-12-12 17:41:58 +01:00
b81b483f0b
First prototype of the scheduler dispatcher is ready... It works, but the code was very difficult...
...
So, when the Scheduler that is passed to the AddScheduler is nillified,
the internal arrays that keep the Scheduler reference are also
nillified. And it does what i need for further utilization in MOOSE
classes. When the Scheduler is nillified, but, a schedule was planned
for that Scheduler, once the scheduler fires off, it will ignore that
call... cool.
Sven
2016-12-12 16:44:56 +01:00
24a6d37500
Progress
2016-12-11 11:01:06 +01:00
46aa9ddf65
Progress
2016-12-10 09:38:35 +01:00
038c10c4d4
Progress
2016-12-10 08:40:49 +01:00
2582e7a90a
Work in progress
...
- problem with UNIT tables... Unit not alive... Need to fix CLIENTs...
CLIENTs need to be copied into UNITs...
2016-12-09 14:48:49 +01:00
8cda04be45
Updates
...
- When joining a slot, you get a mission briefing.
- When task is successful, a message is displayed, and the task is
Success.
- HeadQuarters clears all menus of the involved groups back to Planned.
2016-12-09 13:35:36 +01:00
7c73b232ae
Undone the Templating...
2016-12-09 12:34:43 +01:00
FlightControl