Before an event has been running for the first time, the event can be triggered by a task which is set to STOP the event. This is a bug. After the event has been running once, the tasks starting and stopping the event has the right behaviour.
NB: It might be dangerous to fix this one as it could result in backwards compatibility problems so looking back, I regret I added this. Priority now set to low.
Event can be started by a task set to stop the event
